Triple
T2102089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enlil |
E37112
|
entity |
| Predicate | spouse |
P13
|
FINISHED |
| Object | Ninlil |
E225531
|
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: Ninlil | Statement: [Enlil, spouse, Ninlil]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ninlil Context triple: [Enlil, spouse, Ninlil]
-
A.
Ninlil
chosen
Ninlil is a Mesopotamian goddess, traditionally known as the wife of the god Enlil and associated with air, grain, and the city of Nippur.
-
B.
Inanna
Inanna is the ancient Mesopotamian goddess of love, beauty, sex, war, and political power, later known as Ishtar.
-
C.
Ereshkigal
Ereshkigal is the Mesopotamian goddess who rules the underworld and presides over the realm of the dead.
-
D.
Nanna
Nanna is the Sumerian moon god, a major deity associated with wisdom, fertility, and the measurement of time.
-
E.
Astarte
Astarte is an ancient Near Eastern goddess associated primarily with fertility, sexuality, and war, venerated across Canaanite, Phoenician, and later Mediterranean 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_69a8861828948190924aa30c08806b3a |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69abbabc83a8819091f786f21d33b5a6 |
completed | March 7, 2026, 5:42 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ae6aec3694819090d0e7cf02944aa3 |
completed | March 9, 2026, 6:38 a.m. |
Created at: March 4, 2026, 7:43 p.m.