Triple
T36556140
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dor-en-Ernil |
E901702
|
entity |
| Predicate | hasNúmenóreanHeritage |
P185850
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Dor-en-Ernil, hasNúmenóreanHeritage, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNúmenóreanHeritage Context triple: [Dor-en-Ernil, hasNúmenóreanHeritage, true]
-
A.
noldorinElement
Indicates a relationship where something is identified as an elemental component or fundamental part within the Noldorin linguistic or conceptual system.
-
B.
raceInLegendarium
Indicates that an entity belongs to a particular fictional race or species within a specific mythological or fantasy legendarium.
-
C.
hasMortalOrSemiDivineAncestry
Indicates that an entity descends from, or is otherwise ancestrally connected to, beings who are mortal or possess semi-divine (partly divine) status.
-
D.
hasElvishName
Indicates that an entity possesses a name expressed in the Elvish language.
-
E.
lastHeirOfIsildurToReign
Indicates that the subject is the final reigning ruler who descends from Isildur in the line of succession.
- 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_69f76e634e9481908c9ba1b87ab87c26 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1baf25c8190a78dd54a400d2c50 |
completed | May 3, 2026, 9:44 p.m. |
| PDg | Predicate description generation | batch_69f7c3705b5c81908c84004543a71c07 |
completed | May 3, 2026, 9:51 p.m. |
Created at: May 3, 2026, 4:11 p.m.