Triple
T30169453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | En-men-lu-ana |
E766878
|
entity |
| Predicate | reignBefore |
P175651
|
FINISHED |
| Object | En-men-gal-ana |
—
|
NE NERFINISHED |
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: En-men-gal-ana | Statement: [En-men-lu-ana, reignBefore, En-men-gal-ana]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reignBefore Context triple: [En-men-lu-ana, reignBefore, En-men-gal-ana]
-
A.
reignPreceded
Indicates that one entity’s reign occurred immediately before another entity’s reign in a temporal succession.
-
B.
reignStartBefore
Indicates that the start of one entity’s reign occurs earlier in time than the start of another entity’s reign.
-
C.
reignAfter
Indicates that one entity begins its reign or rule following the conclusion of another entity's reign.
-
D.
reignTo
Indicates that one entity exercises ruling authority or governance over another entity or domain during a particular period.
-
E.
precedesInReign
chosen
Indicates that one ruler’s period of reign occurred entirely before another ruler’s period of reign in a temporal succession.
- 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_69f727afd5d88190ad48735cd1b32787 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72737c42c8190a3f781a5e98868ff |
completed | May 3, 2026, 10:45 a.m. |
Created at: April 29, 2026, 7:24 p.m.