Triple
T9662149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Humbaba |
E233614
|
entity |
| Predicate | killedBy |
P4646
|
FINISHED |
| Object | Enkidu |
E233611
|
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: Enkidu | Statement: [Humbaba, killedBy, Enkidu]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Enkidu Context triple: [Humbaba, killedBy, Enkidu]
-
A.
Enkidu
chosen
Enkidu is a wild man created by the gods who becomes the close companion and moral counterbalance to King Gilgamesh in ancient Mesopotamian mythology.
-
B.
Ninurta
Ninurta is a Mesopotamian god associated with war, hunting, and agriculture, often depicted as a heroic warrior and champion of the god Enlil.
-
C.
Dumuzi
Dumuzi is a Sumerian shepherd god associated with fertility, vegetation, and seasonal cycles, best known from Mesopotamian myths of death and rebirth.
-
D.
Enmerkar
Enmerkar is a legendary Sumerian king of Uruk, best known from ancient Mesopotamian epics that depict his rivalries, quests, and early developments in writing and civilization.
-
E.
Adad-happe
Adad-happe was a Neo-Babylonian queen, known primarily as the wife of King Nabopolassar and mother of his royal heirs.
- 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_69ca848d3b6c8190ae98ea554dea58df |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9c0b7728819099473f404382b26a |
completed | April 1, 2026, 10:28 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d19f6d397481908f7db1f272a6a710 |
completed | April 4, 2026, 11:31 p.m. |
Created at: March 30, 2026, 8:14 p.m.