Triple
T27553951
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Númenor |
E695583
|
entity |
| Predicate | successorPeoples |
P36302
|
FINISHED |
| Object | Dúnedain of the North |
—
|
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: Dúnedain of the North | Statement: [Númenor, successorPeoples, Dúnedain of the North]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorPeoples Context triple: [Númenor, successorPeoples, Dúnedain of the North]
-
A.
successorDynasty
Indicates that one dynasty directly follows and replaces another in a sequence of rule or authority.
-
B.
possibleSuccessorPeoples
chosen
Indicates that one group of people is a potential successor or replacement for another group in a given context or role.
-
C.
successorInNorthernLands
Indicates that one entity becomes the next holder of a role, title, or position specifically within the context of the Northern Lands.
-
D.
successorInCountry
Indicates that one entity takes over a role, position, or function from another entity within the same country.
-
E.
successorDynastyOrigin
Indicates the place or cultural-geographic origin from which a successor dynasty arises in relation to its predecessor.
- 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_69ef5387e97c8190a9dab040d21cd048 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69fba78aca4c8190b8f1831e8cc04e06 |
completed | May 6, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69fba34a65a4819088bac6c17542d71c |
completed | May 6, 2026, 8:23 p.m. |
Created at: April 27, 2026, 1:36 p.m.