Triple
T26220180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viscount Bruce of Melbourne |
E655743
|
entity |
| Predicate | extinctReason |
P6998
|
FINISHED |
| Object | death of first viscount without male 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 viscount without male heirs | Statement: [Viscount Bruce of Melbourne, extinctReason, death of first viscount without male heirs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: extinctReason Context triple: [Viscount Bruce of Melbourne, extinctReason, death of first viscount without male heirs]
-
A.
extinctionReason
chosen
Indicates the cause or factor responsible for an entity’s extinction.
-
B.
extinctionDate
Indicates the date or time at which an entity (typically a species or lineage) ceased to exist.
-
C.
extinctionType
Indicates the specific manner or category by which an entity ceases to exist or becomes extinct.
-
D.
extinct
Indicates that the referenced entity no longer exists as a living or active member of its former kind or category.
-
E.
titleExtinct
Indicates that a formal title or rank is no longer in existence or officially recognized.
- 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_69ee5b4a77e08190bfcb5f8ecdc55abd |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f60d4f66748190819e060ab3dc492c |
completed | May 2, 2026, 2:42 p.m. |
| PD | Predicate disambiguation | batch_69f5b007ec1c819092e2c3605933f60b |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 26, 2026, 8:55 p.m.