Triple
T651783
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nebuchadnezzar II |
E11359
|
entity |
| Predicate | patronDeity |
P5606
|
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: [Nebuchadnezzar II, patronDeity, Marduk]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Marduk Context triple: [Nebuchadnezzar II, patronDeity, 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.
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.
-
D.
Enlil
Enlil is a chief god in ancient Mesopotamian religion, associated with wind, air, and authority over the cosmos.
-
E.
Baal
Baal is a prominent ancient Near Eastern storm and fertility god widely worshipped across Phoenician and Canaanite cultures.
- 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_69a493266a2881909daf4c40f719dee8 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49f35acb08190a3a8248023ce07f9 |
completed | March 1, 2026, 8:19 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a6732a8c0881909753261f9256fcf2 |
completed | March 3, 2026, 5:35 a.m. |
Created at: March 1, 2026, 7:36 p.m.