Triple
T15703353
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shamshi-Adad I |
E380647
|
entity |
| Predicate | capital |
P234
|
FINISHED |
| Object | Ekallatum |
E1171870
|
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: Ekallatum | Statement: [Shamshi-Adad I, capital, Ekallatum]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ekallatum Context triple: [Shamshi-Adad I, capital, Ekallatum]
-
A.
Ekallatum
chosen
Ekallatum was an ancient Mesopotamian city-state on the Tigris River that became an important power center in northern Babylonia during the early second millennium BCE.
-
B.
Ninhursag
Ninhursag is a major Sumerian mother goddess associated with fertility, mountains, and the earth.
-
C.
Eshmun
Eshmun is a Phoenician god primarily associated with healing and medicine, often linked to later Greco-Roman healing deities.
-
D.
Ninshubur
Ninshubur is a Mesopotamian deity known primarily as the loyal sukkal (divine vizier and attendant) and messenger of the goddess Inanna.
-
E.
Asherah
Asherah is an ancient West Semitic mother goddess associated with fertility, the sea, and sacred trees, venerated across Canaan and neighboring 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_69d86d9bf930819082b30cf6d169297c |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e04f6e965881909319f85c51c6fb74 |
completed | April 16, 2026, 2:54 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff82f05d648190a0c73b60dc027287 |
completed | May 9, 2026, 6:54 p.m. |
Created at: April 10, 2026, 4:45 a.m.