Triple
T11492068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peregrin Took |
E272438
|
entity |
| Predicate | becameThainInYear |
P99782
|
FINISHED |
| Object | Fourth Age 13 |
—
|
LITERAL FINISHED |
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: Fourth Age 13 | Statement: [Peregrin Took, becameThainInYear, Fourth Age 13]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: becameThainInYear Context triple: [Peregrin Took, becameThainInYear, Fourth Age 13]
-
A.
ascendedThroneYear
Indicates the year in which a person formally ascended to or took possession of a throne or ruling position.
-
B.
royalDesignationYear
Indicates the year in which an entity was formally granted or recognized with a royal status or designation.
-
C.
placedOnThrone
Indicates that an entity is formally elevated to a position of rulership or authority, typically by being seated on a throne.
-
D.
cameIntoForceInYear
Indicates that a law, agreement, or formal measure became legally effective or operational in a specified calendar year.
-
E.
successorAdoptionYear
Indicates the year in which a successor entity formally adopted or took over from its predecessor.
- F. None of above. chosen
Provenance (4 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_69d6aae1b09881909ce2ded3fa0c14fa |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d85a21fb048190acb0960aefd4fe0a |
completed | April 10, 2026, 2:02 a.m. |
| PD | Predicate disambiguation | batch_69d808736c5c8190899b5b3b2e797f65 |
completed | April 9, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69d822ef46988190a1c360da4ee14fef |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 8, 2026, 9:36 p.m.