Triple
T36843827
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Angmar War |
E910484
|
entity |
| Predicate | outcomeForWitchKing |
P186721
|
FINISHED |
| Object | flight to Mordor |
—
|
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: flight to Mordor | Statement: [Angmar War, outcomeForWitchKing, flight to Mordor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: outcomeForWitchKing Context triple: [Angmar War, outcomeForWitchKing, flight to Mordor]
-
A.
outcomeForGandalf
Indicates the result or consequence that specifically befalls Gandalf in a given situation or event.
-
B.
outcomeForSith
Indicates the resulting state, consequence, or effect that an event, action, or situation has specifically for a Sith.
-
C.
outcomeForAngmar
Indicates the result, consequence, or final state that occurs specifically for Angmar in a given event or situation.
-
D.
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.
-
E.
statusAfterBattleOfFiveArmies
Indicates the condition or state of an entity following the events of the Battle of Five Armies.
- 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_69f76e7f65a881908651b702da592b6d |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fa0a7b00948190a257273d9968c5d7 |
completed | May 5, 2026, 3:19 p.m. |
| PD | Predicate disambiguation | batch_69f9fec9c9488190ae2a349651a02782 |
completed | May 5, 2026, 2:29 p.m. |
| PDg | Predicate description generation | batch_69fa0a799b9081909bfa8293a22c4b00 |
completed | May 5, 2026, 3:19 p.m. |
Created at: May 3, 2026, 4:13 p.m.