Triple
T36557513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wars of Angmar against Arnor |
E901734
|
entity |
| Predicate | hasAllyOfArnor |
P146243
|
FINISHED |
| Object | Círdan’s Elves of Lindon |
—
|
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: Círdan’s Elves of Lindon | Statement: [Wars of Angmar against Arnor, hasAllyOfArnor, Círdan’s Elves of Lindon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAllyOfArnor Context triple: [Wars of Angmar against Arnor, hasAllyOfArnor, Círdan’s Elves of Lindon]
-
A.
hasNúmenóreanHeritage
Indicates that one entity possesses ancestral lineage or descent connected to the Númenóreans.
-
B.
sideInWarOfTheRing
Indicates the faction or alignment a participant belongs to in the context of the War of the Ring conflict.
-
C.
hasAllyHouse
Indicates that one house maintains an alliance or supportive partnership with another house.
-
D.
brotherOrAlly
Indicates a relationship where one entity is either a brother of, or an allied supporter/partner to, another entity.
-
E.
vassalOrAllyOf
chosen
Indicates that one entity is subordinate to, dependent on, or formally aligned in support of another entity, typically in a hierarchical or cooperative political or military relationship.
- 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_69fe163a41a0819098403b470e327d29 |
completed | May 8, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fe1358db5c819092570814a37ef5bd |
completed | May 8, 2026, 4:46 p.m. |
Created at: May 3, 2026, 4:11 p.m.