Triple
T18694138
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ziusudra |
E457071
|
entity |
| Predicate | grantedBy |
P2246
|
FINISHED |
| Object | god Enlil |
—
|
NE NERFINISHED |
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: god Enlil | Statement: [Ziusudra, grantedBy, god Enlil]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: god Enlil Context triple: [Ziusudra, grantedBy, god Enlil]
-
A.
Enlil
chosen
Enlil is a chief god in ancient Mesopotamian religion, associated with wind, air, and authority over the cosmos.
-
B.
Akkadian god Anu
Akkadian god Anu is the Mesopotamian sky god and supreme deity of the pantheon, associated with authority, kingship, and the celestial realm.
-
C.
Enki
Enki is a major Sumerian god associated with water, wisdom, creation, and magic, often depicted as a benefactor of humanity and a master of divine knowledge.
-
D.
Marduk
Marduk is the chief god of Babylon in ancient Mesopotamian religion, associated with creation, kingship, and the defeat of the chaos monster Tiamat.
-
E.
God of Nahor
The God of Nahor is the deity worshiped by Nahor, Abraham’s brother, in the Hebrew Bible, representing the ancestral god of his family line.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8d391eb488190ac2e9abf5bf255e4 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e562e581f48190997d279296a31e7f |
completed | April 19, 2026, 11:19 p.m. |
Created at: April 10, 2026, 11:49 a.m.