Triple
T36557798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wainriders |
E901740
|
entity |
| Predicate | opponentInBattleOfTheMorannon |
P186517
|
FINISHED |
| Object | King Ondoher of Gondor |
—
|
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: King Ondoher of Gondor | Statement: [Wainriders, opponentInBattleOfTheMorannon, King Ondoher of Gondor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opponentInBattleOfTheMorannon Context triple: [Wainriders, opponentInBattleOfTheMorannon, King Ondoher of Gondor]
-
A.
ElrosChose
Indicates that Elros made a deliberate choice or selection among available options.
-
B.
ElrondChose
Indicates that Elrond made a deliberate selection or decision regarding a particular option, entity, or course of action.
-
C.
timeOfExpulsionOfSauronFromDolGuldur
Indicates the point in time at which Sauron was driven out or expelled from Dol Guldur.
-
D.
roleInBattleOfFiveArmies
Indicates the specific function, position, or involvement an entity had in the Battle of Five Armies.
-
E.
Listoghil
Indicates a relationship in which an entity is associated with or belongs to the place or context referred to as Listoghil.
- F. None of above. chosen
Provenance (4 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_69f76e634e9481908c9ba1b87ab87c26 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f9fe1a1ca4819084c196f0041f0be2 |
completed | May 5, 2026, 2:26 p.m. |
| PD | Predicate disambiguation | batch_69f7cf769338819092a5f42653dcc956 |
completed | May 3, 2026, 10:43 p.m. |
| PDg | Predicate description generation | batch_69f9fd66eed48190bdc26a8def328c2d |
completed | May 5, 2026, 2:23 p.m. |
Created at: May 3, 2026, 4:11 p.m.