Q52, run 2026-11-04-2024-sonnet-query

← back to the run

How many entities are in the Rotam Group Inc group, the parent included?

Tests: Paths and sources: a RESEARCH record names this top as a parent, but RATINGS holds for parent links.

Expected: count = 19

✅ D1 sql run 1 graded by code · query session

19. E5168 is a research duplicate of Belir Mining and is merged out.

JSON: {"count": 19}

❌ D1 sql run 2 graded by code · query session

20.

JSON: {"count": 20}

Why: count: expected 19, got 20

❌ D1 sql run 3 graded by code · query session

20.

JSON: {"count": 20}

Why: count: expected 19, got 20

❌ D2 sql+markdown run 1 graded by code · query session

3.

JSON: {"count": 3}

Why: count: expected 19, got 3

✅ D2 sql+markdown run 2 graded by code · query session

19.

JSON: {"count": 19}

✅ D2 sql+markdown run 3 graded by code · query session

19.

JSON: {"count": 19}

❌ D4 sparql run 1 graded by code · query session

(no answer found)

JSON: {"count": 0}

Why: count: expected 19, got 0

❌ D4 sparql run 2 graded by code · query session

20. This is uncertain because of duplicate records such as E5168.

JSON: {"count": 20}

Why: count: expected 19, got 20

❌ D4 sparql run 3 graded by code · query session

(no answer found)

JSON: {"count": 0}

Why: count: expected 19, got 0

✅ D5 sparql+ontology run 1 graded by code · query session

19. I excluded the Belir branch, because RESEARCH's parent link on E5168 conflicts with RATINGS, which holds for parent links.

JSON: {"count": 19}

✅ D5 sparql+ontology run 2 graded by code · query session

19, which is E5086 to E5104. The RESEARCH record E5168 gives Belir Mining a parent in the Rotam group, but RATINGS holds for parent links and puts Belir Mining under E5060, then E5059.

JSON: {"count": 19}

✅ D5 sparql+ontology run 3 graded by code · query session

19.

JSON: {"count": 19}

✅ D3 sql+executed run 1 graded by code · query session

19 entities: 18 plus E5086.

JSON: {"count": 19}

✅ D3 sql+executed run 2 graded by code · query session

19.

JSON: {"count": 19}

✅ D3 sql+executed run 3 graded by code · query session

19.

JSON: {"count": 19}

✅ D6 sparql+axioms run 1 graded by code · query session

19 (E5086–E5104).

JSON: {"count": 19}

❌ D6 sparql+axioms run 2 graded by code · query session

(no answer found)

JSON: {"count": 0}

Why: count: expected 19, got 0

✅ D6 sparql+axioms run 3 graded by code · query session

19.

JSON: {"count": 19}