Triple
T36549645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thain |
E901223
|
entity |
| Predicate | successorAfterWarOfTheRing |
P97501
|
FINISHED |
| Object | Peregrin Took |
—
|
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: Peregrin Took | Statement: [Thain, successorAfterWarOfTheRing, Peregrin Took]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorAfterWarOfTheRing Context triple: [Thain, successorAfterWarOfTheRing, Peregrin Took]
-
A.
lastHeirOfIsildurToReign
Indicates that the subject is the final reigning ruler who descends from Isildur in the line of succession.
-
B.
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.
-
C.
ledByDuringWarOfTheRing
Indicates that an individual or group served as the leader of another entity specifically during the period of the War of the Ring.
-
D.
successorAsKingOfKings
Indicates that one entity directly follows another in holding the title or role of King of Kings.
-
E.
statusAfterWarOfTheRing
chosen
Indicates the condition or role an entity has following the events of the War of the Ring.
- 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_69f76e61217081908b79d610fe67b013 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a007aa8d3a481908543f9b5d562a90c |
completed | May 10, 2026, 12:31 p.m. |
| PD | Predicate disambiguation | batch_6a007a44996481908688ccfdbc56511d |
completed | May 10, 2026, 12:29 p.m. |
Created at: May 3, 2026, 4:11 p.m.