Triple
T1259102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baron Keynes of Tilton |
E12457
|
entity |
| Predicate | reasonForExtinction |
P6998
|
FINISHED |
| Object | death of first holder without heirs |
—
|
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: death of first holder without heirs | Statement: [Baron Keynes of Tilton, reasonForExtinction, death of first holder without heirs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForExtinction Context triple: [Baron Keynes of Tilton, reasonForExtinction, death of first holder without heirs]
-
A.
extinctionReason
chosen
Indicates the cause or factor responsible for an entity’s extinction.
-
B.
extinctionType
Indicates the specific manner or category by which an entity ceases to exist or becomes extinct.
-
C.
extinct
Indicates that the referenced entity no longer exists as a living or active member of its former kind or category.
-
D.
creationCanBecomeExtinct
Indicates that something which has been created is capable of ceasing to exist or becoming extinct.
-
E.
extinctionPeriod
Indicates the time span during which an entity ceases to exist or is considered extinct.
- 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_69a4933352e08190ac617291985e76c0 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4bfc3a2848190891e73b351019d5b |
completed | March 1, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69a4bb6eefbc81908dddd7d2ef368186 |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:50 p.m.