Triple
T9661749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord Wind |
E233605
|
entity |
| Predicate | relatedDeity |
P23286
|
FINISHED |
| Object | Enlil |
E37112
|
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: Enlil | Statement: [Lord Wind, relatedDeity, Enlil]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Enlil Context triple: [Lord Wind, relatedDeity, Enlil]
-
A.
Enlil
chosen
Enlil is a chief god in ancient Mesopotamian religion, associated with wind, air, and authority over the cosmos.
-
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.
Marduk
Marduk is the chief god of Babylon in ancient Mesopotamian religion, associated with creation, kingship, and the defeat of the chaos monster Tiamat.
-
D.
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.
-
E.
Enlil-nirari
Enlil-nirari was a Middle Assyrian king who ruled the Assyrian Empire in the 14th century BCE, helping to consolidate its growing regional power.
- 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_69d6525a4af08190bcd8455e95a2f3ae |
completed | April 8, 2026, 1:04 p.m. |
Created at: March 30, 2026, 8:14 p.m.