Triple
T8925839
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nanna |
E212536
|
entity |
| Predicate | spouse |
P13
|
FINISHED |
| Object | Ningal |
E258526
|
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: Ningal | Statement: [Nanna, spouse, Ningal]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ningal Context triple: [Nanna, spouse, Ningal]
-
A.
Tarḫunna
Tarḫunna is the chief storm god of the Hittite pantheon, associated with thunder, rain, and kingship.
-
B.
Eshmun
Eshmun is a Phoenician god primarily associated with healing and medicine, often linked to later Greco-Roman healing deities.
-
C.
Anahita
Anahita is an ancient Iranian goddess associated with water, fertility, and protection, widely venerated in the Achaemenid and later Persian empires.
-
D.
Ninhursag
chosen
Ninhursag is a major Sumerian mother goddess associated with fertility, mountains, and the earth.
-
E.
Ninlil
Ninlil is a Mesopotamian goddess, traditionally known as the wife of the god Enlil and associated with air, grain, and the city of Nippur.
- 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_69ca839481d48190b42b037e0d0f636c |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc66700fb48190874563e535f20437 |
completed | April 1, 2026, 12:27 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cffd8495488190a1d93f9e5b7e334d |
completed | April 3, 2026, 5:48 p.m. |
Created at: March 30, 2026, 6:57 p.m.