Triple
T9256999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dukes of Richmond |
E222468
|
entity |
| Predicate | thirdCreationExtinctionReason |
P6998
|
FINISHED |
| Object | died without surviving male issue |
—
|
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: died without surviving male issue | Statement: [Dukes of Richmond, thirdCreationExtinctionReason, died without surviving male issue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: thirdCreationExtinctionReason Context triple: [Dukes of Richmond, thirdCreationExtinctionReason, died without surviving male issue]
-
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.
reasonForCreation
Indicates that one entity was created for the purpose, cause, or motivation specified by another entity.
-
D.
creationCanBecomeExtinct
Indicates that something which has been created is capable of ceasing to exist or becoming extinct.
-
E.
extinctionEvent
Indicates a large-scale occurrence that causes the widespread or complete disappearance of one or more species or higher taxonomic groups.
- 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_69ca841e4cd481908e738c74e958eaea |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd06b4e2048190af0d65b904677c36 |
completed | April 1, 2026, 11:51 a.m. |
| PD | Predicate disambiguation | batch_69cc7a4e79e48190b3200247f4624867 |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:32 p.m.