Triple
T36843807
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Angmar War |
E910484
|
entity |
| Predicate | involvesAlliesOfArnor |
P133749
|
FINISHED |
| Object | 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: Lindon | Statement: [Angmar War, involvesAlliesOfArnor, Lindon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvesAlliesOfArnor Context triple: [Angmar War, involvesAlliesOfArnor, Lindon]
-
A.
sideInWarOfTheRing
Indicates the faction or alignment a participant belongs to in the context of the War of the Ring conflict.
-
B.
alliesIncluded
Indicates that the specified set or group explicitly includes one or more allied entities as members.
-
C.
involvesAlliance
chosen
Indicates that there exists a cooperative or strategic alliance relationship between the referenced entities.
-
D.
vassalOrAllyOf
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.
-
E.
oftenAlliedWith
Indicates that one entity is frequently or habitually allied or aligned in cooperation with another entity.
- 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_69f76e7f65a881908651b702da592b6d |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fe7bfc94bc81909eeec946e8c1c450 |
completed | May 9, 2026, 12:12 a.m. |
| PD | Predicate disambiguation | batch_69fe7b74a1188190886f128e07f712da |
completed | May 9, 2026, 12:10 a.m. |
Created at: May 3, 2026, 4:13 p.m.