Triple
T33381569
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kings of Gondor |
E854795
|
entity |
| Predicate | kingshipRestoredBy |
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: [Kings of Gondor, kingshipRestoredBy, Aragorn II Elessar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: kingshipRestoredBy Context triple: [Kings of Gondor, kingshipRestoredBy, Aragorn II Elessar]
-
A.
restoredToThroneBy
chosen
Indicates that an entity was returned to a position of rulership or kingship through the actions or intervention of another entity.
-
B.
firstMonarchAfterRestoration
Indicates the monarch who was the first to assume the throne following a period of restoration of the monarchy or regime.
-
C.
restoredToThrone
Indicates that an entity regains a previously held throne or royal position after having lost or been removed from it.
-
D.
regainsThroneFrom
Indicates that one entity takes back control of a throne or rulership position that had been held by another entity.
-
E.
reignAssociatedWith
Indicates a relationship where a period of rule or reign is connected to a specific person, position, or governing entity.
- 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_69f3496ca10c8190908640d18fa00832 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e002526881909ffee65161b1a6e1 |
completed | May 3, 2026, 5:41 a.m. |
| PD | Predicate disambiguation | batch_69f6de0c821c8190ae3ebda9dfdd0064 |
completed | May 3, 2026, 5:33 a.m. |
Created at: May 1, 2026, 1:35 a.m.