Triple
T33111931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dúnedain of the North |
E847352
|
entity |
| Predicate | royalLineagePreservedFrom |
P57937
|
FINISHED |
| Object | Isildur |
—
|
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: Isildur | Statement: [Dúnedain of the North, royalLineagePreservedFrom, Isildur]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: royalLineagePreservedFrom Context triple: [Dúnedain of the North, royalLineagePreservedFrom, Isildur]
-
A.
hasRoyalAncestryFrom
chosen
Indicates that one entity possesses royal lineage or descent originating from another entity.
-
B.
dynasticInheritance
Indicates that rights, titles, or property are passed down through a family line according to established rules of succession.
-
C.
hasBranchOfImperialFamily
Indicates that an entity includes or is associated with a specific branch or lineage of an imperial family.
-
D.
heirThroughFemaleLine
Indicates that one entity is the heir of another specifically through a lineage traced via female ancestors.
-
E.
generationWithinImperialFamily
Indicates the ordinal generation level of an individual within an imperial family lineage (e.g., first generation, second generation).
- 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_69f3495751a081909850af5843da40dc |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d6eb33648190b26122f53c88d8eb |
completed | May 3, 2026, 5:02 a.m. |
| PD | Predicate disambiguation | batch_69f6d27224708190b31a541cebe0ff77 |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:27 a.m.