Triple
T36557783
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wainriders |
E901740
|
entity |
| Predicate | defeatedKingOfGondor |
P11263
|
FINISHED |
| Object | Narmacil II |
—
|
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: Narmacil II | Statement: [Wainriders, defeatedKingOfGondor, Narmacil II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defeatedKingOfGondor Context triple: [Wainriders, defeatedKingOfGondor, Narmacil II]
-
A.
lastHeirOfIsildurToReign
Indicates that the subject is the final reigning ruler who descends from Isildur in the line of succession.
-
B.
lastKingBeforeStewards
Indicates that one entity is the final king who ruled immediately prior to the period when stewards assumed governing authority over the other entity.
-
C.
eventuallyDefeatedBy
Indicates that one entity is ultimately overcome, beaten, or conquered by another, possibly after some duration or sequence of events.
-
D.
defeatedBy
chosen
Indicates that one entity has been beaten, overcome, or conquered by another in a contest, conflict, or competition.
-
E.
outcomeForGandalf
Indicates the result or consequence that specifically befalls Gandalf in a given situation or event.
- 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_69f76e634e9481908c9ba1b87ab87c26 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1baf25c8190a78dd54a400d2c50 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:11 p.m.