Triple
T37142984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Green-elves of Ossiriand |
E920165
|
entity |
| Predicate | ancestorGroup |
P35417
|
FINISHED |
| Object | Nandor |
E1991945
|
NE 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: Nandor | Statement: [Green-elves of Ossiriand, ancestorGroup, Nandor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ancestorGroup Context triple: [Green-elves of Ossiriand, ancestorGroup, Nandor]
-
A.
ancestralGroup
chosen
Indicates that one entity is a broader ancestral lineage, population, or group from which the other entity descends or originates.
-
B.
ancestor
Indicates that one entity is a forebear of another in a lineage, occurring in an earlier generation and connected through one or more parent-child relationships.
-
C.
ancestorMother
Indicates that one entity is a female ancestor (mother, grandmother, etc.) of another entity in a family lineage.
-
D.
ancestorHouse
Indicates that one entity is the house or dwelling associated with the ancestors of another entity.
-
E.
ancestorDescribedAs
Indicates that an ancestor is characterized or referred to using a particular description, label, or portrayal.
- F. None of above.
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_69f76e9e9d008190a250b0387c992c74 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb344c60f8819090f2e21e1e61d621 |
completed | May 6, 2026, 12:30 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3f6a2b63048190bdfc955ff038baed |
completed | June 27, 2026, 6:14 a.m. |
| PD | Predicate disambiguation | batch_69fb2f642db08190b562725502c74ea6 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:15 p.m.