Triple
T36843826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Angmar War |
E910484
|
entity |
| Predicate | outcomeForAngmar |
P186574
|
FINISHED |
| Object | destruction of Angmar as a kingdom |
—
|
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: destruction of Angmar as a kingdom | Statement: [Angmar War, outcomeForAngmar, destruction of Angmar as a kingdom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: outcomeForAngmar Context triple: [Angmar War, outcomeForAngmar, destruction of Angmar as a kingdom]
-
A.
outcomeForGandalf
Indicates the result or consequence that specifically befalls Gandalf in a given situation or event.
-
B.
eventualSideAtRagnarök
Indicates the side or faction an entity will ultimately align with or belong to during Ragnarök.
-
C.
Listoghil
Indicates a relationship in which an entity is associated with or belongs to the place or context referred to as Listoghil.
-
D.
actionAtRagnarök
Indicates an action or event that is specifically performed or occurs during Ragnarök, the final apocalyptic battle in Norse mythology.
-
E.
outcomeForAlamanni
Indicates the result, consequence, or impact that a particular event, action, or situation has specifically for the Alamanni.
- 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_69f9fe1a1ca4819084c196f0041f0be2 |
completed | May 5, 2026, 2:26 p.m. |
| PD | Predicate disambiguation | batch_69f7cf7890008190a8bc355ff2d61c86 |
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:13 p.m.