Triple
T33111957
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dúnedain of the North |
E847352
|
entity |
| Predicate | restoredKingshipThrough |
P57955
|
FINISHED |
| Object | Aragorn II Elessar |
—
|
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: Aragorn II Elessar | Statement: [Dúnedain of the North, restoredKingshipThrough, Aragorn II Elessar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: restoredKingshipThrough Context triple: [Dúnedain of the North, restoredKingshipThrough, Aragorn II Elessar]
-
A.
restoredToThrone
Indicates that an entity regains a previously held throne or royal position after having lost or been removed from it.
-
B.
restoredToThroneBy
chosen
Indicates that an entity was returned to a position of rulership or kingship through the actions or intervention of another entity.
-
C.
regainsThroneFrom
Indicates that one entity takes back control of a throne or rulership position that had been held by another entity.
-
D.
dynastyRestored
Indicates that a previously displaced ruling dynasty has been returned to power or reestablished as the legitimate authority.
-
E.
heldByBeforeKingship
Indicates that an office, role, or position was held by a person prior to that person attaining kingship.
- 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_69f6f8164698819090c1b471f1caa4c6 |
completed | May 3, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69f6f6619404819084662aef1238261c |
completed | May 3, 2026, 7:16 a.m. |
Created at: May 1, 2026, 1:27 a.m.