Triple
T28889767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dúnedain of Gondor |
E732664
|
entity |
| Predicate | hasDescentFrom |
P33454
|
FINISHED |
| Object | Edain |
—
|
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: Edain | Statement: [Dúnedain of Gondor, hasDescentFrom, Edain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDescentFrom Context triple: [Dúnedain of Gondor, hasDescentFrom, Edain]
-
A.
hasDescentTo
Indicates that one entity is a descendant of another, connected through a line of ancestry or lineage.
-
B.
hasDescent
Indicates that one entity is a descendant of another, typically through a lineage or ancestry relationship.
-
C.
hasTypeOfDescent
Indicates that one entity possesses a particular kind or category of ancestral or lineage-based origin in relation to another entity.
-
D.
descentFrom
chosen
Indicates that one entity is a descendant of another, typically through a lineage or ancestral relationship.
-
E.
alsoHasAncestry
Indicates that an entity possesses an additional ancestral lineage or heritage beyond its primary recorded ancestry.
- 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_69f05b07bdec819080cadfe147aa1f25 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69fd09840ea88190a2e6d7e577ade717 |
completed | May 7, 2026, 9:52 p.m. |
| PD | Predicate disambiguation | batch_69fd064c49988190afadddbd04d7cb94 |
completed | May 7, 2026, 9:38 p.m. |
Created at: April 28, 2026, 7:54 a.m.