Triple
T16050177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tashrītu |
E389331
|
entity |
| Predicate | associatedDeity |
P1481
|
FINISHED |
| Object | Marduk |
E38028
|
NE FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Marduk | Statement: [Tashrītu, associatedDeity, Marduk]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Marduk Context triple: [Tashrītu, associatedDeity, Marduk]
-
A.
Marduk
chosen
Marduk is the chief god of Babylon in ancient Mesopotamian religion, associated with creation, kingship, and the defeat of the chaos monster Tiamat.
-
B.
Labashi-Marduk
Labashi-Marduk was a short-reigning Neo-Babylonian king, likely the son of Neriglissar, who was overthrown in a conspiracy soon after ascending the throne in the 6th century BCE.
-
C.
Ninurta
Ninurta is a Mesopotamian god associated with war, hunting, and agriculture, often depicted as a heroic warrior and champion of the god Enlil.
-
D.
Amel-Marduk
Amel-Marduk was a 6th-century BCE king of Babylon, known from biblical and cuneiform sources as the successor of Nebuchadnezzar II and for releasing the Judean king Jehoiachin from prison.
-
E.
Nergal
Nergal is an ancient Mesopotamian god associated primarily with war, plague, and the underworld.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69d86dae698881908327ef2d67706cb9 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e18361083c8190abc84534265dc992 |
completed | April 17, 2026, 12:48 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fff796fafc8190b6cfb2d8ea502eef |
completed | May 10, 2026, 3:12 a.m. |
Created at: April 10, 2026, 4:56 a.m.