Triple
T33111926
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dúnedain of the North |
E847352
|
entity |
| Predicate | laterSeatOfKings |
P121240
|
FINISHED |
| Object | Fornost Erain |
—
|
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: Fornost Erain | Statement: [Dúnedain of the North, laterSeatOfKings, Fornost Erain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterSeatOfKings Context triple: [Dúnedain of the North, laterSeatOfKings, Fornost Erain]
-
A.
lastKingBeforeStewards
Indicates that one entity is the final king who ruled immediately prior to the period when stewards assumed governing authority over the other entity.
-
B.
laterFamilySeat
chosen
Indicates that one entity serves as a subsequent or later seat, residence, or base for a particular family or lineage, following an earlier one.
-
C.
lostThroneTo
Indicates that one entity was previously in possession of a throne or rulership but was defeated or displaced so that another entity took that throne instead.
-
D.
hadKingdom
Indicates that an entity possessed or ruled over a particular kingdom.
-
E.
laterHeir
Indicates that one entity becomes the heir of another at a later time, succeeding a prior heir or following a change in succession.
- 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_69ffc1550cb481908628e446d9b67f7b |
completed | May 9, 2026, 11:20 p.m. |
| PD | Predicate disambiguation | batch_69ffc10a74708190ae90e2c378791f70 |
completed | May 9, 2026, 11:19 p.m. |
Created at: May 1, 2026, 1:27 a.m.