Triple
T23924551
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duke of Neuburg |
E602308
|
entity |
| Predicate | titleExtinctInPractice |
P124453
|
FINISHED |
| Object | 18th century |
—
|
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: 18th century | Statement: [Duke of Neuburg, titleExtinctInPractice, 18th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleExtinctInPractice Context triple: [Duke of Neuburg, titleExtinctInPractice, 18th century]
-
A.
titleExtinct
chosen
Indicates that a formal title or rank is no longer in existence or officially recognized.
-
B.
possiblyExtinctBy
Indicates that an entity is believed or suspected to have gone extinct as a result of the specified cause or agent.
-
C.
thoughtExtinct
Indicates that something was previously believed to no longer exist or to have died out, but is now recognized or suggested to still exist.
-
D.
hasExtinction
Indicates that an entity has undergone, is subject to, or is associated with an extinction event or state of no longer existing.
-
E.
possiblyExtinctInTheWild
Indicates that the species may no longer exist in natural habitats and might survive, if at all, only in captivity or cultivation.
- 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_69e2953b928c819095395fa87baca583 |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f1cf1bdf108190b3c04146af8c3b3c |
completed | April 29, 2026, 9:27 a.m. |
| PD | Predicate disambiguation | batch_69f16151ebdc819086e9e1d7cc1f4f3c |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:42 p.m.