Triple
T30168354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enki and the World Order |
E766853
|
entity |
| Predicate | roleOfEnki |
P2319
|
FINISHED |
| Object | organizer of the cosmos |
—
|
LITERAL 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: organizer of the cosmos | Statement: [Enki and the World Order, roleOfEnki, organizer of the cosmos]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleOfEnki Context triple: [Enki and the World Order, roleOfEnki, organizer of the cosmos]
-
A.
roleInKojiki
Indicates the role or function an entity holds within the narrative or structure of the Kojiki.
-
B.
roleInRitual
Indicates the specific function, position, or responsibility an entity holds within a particular ritual or ceremonial activity.
-
C.
roleInBladeTrinity
Indicates that an entity participated in the movie "Blade: Trinity" in a specific role (such as actor, director, or crew position).
-
D.
roleInTheology
chosen
Indicates the specific function, position, or significance an entity holds within a theological system, doctrine, or belief framework.
-
E.
roleInShinto
Indicates that an entity holds a particular function, status, or significance within the context of Shinto beliefs, practices, or institutions.
- F. None of above.
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_69f2247a968881909d79c18f2bfcb275 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6a916d2e08190bafc01cba73b6469 |
completed | May 3, 2026, 1:47 a.m. |
| PD | Predicate disambiguation | batch_69f6a7548eb48190a69b60a3c6ad53b9 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 29, 2026, 7:23 p.m.