Triple
T16114193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Richelieu family |
E390960
|
entity |
| Predicate | extinctionOfMainDucalLine |
P48008
|
FINISHED |
| Object | 19th 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: 19th century | Statement: [Richelieu family, extinctionOfMainDucalLine, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: extinctionOfMainDucalLine Context triple: [Richelieu family, extinctionOfMainDucalLine, 19th century]
-
A.
endedDirectMaleLineOfHouseOfCapet
Indicates that a person’s actions or circumstances brought about the end of the uninterrupted male-line succession of the House of Capet.
-
B.
extinctDynasty
Indicates that a dynasty has ceased to exist and no longer continues through ruling descendants or recognized lineage.
-
C.
successorAsDukeOfSavoy
Indicates that one entity became the next Duke of Savoy following another entity in the line of succession.
-
D.
extinctionOfMaleLine
chosen
Indicates that a family’s direct male lineage has ended, with no surviving male descendants to continue it.
-
E.
lastSovereignDuke
Indicates that the subject is the final individual to hold the title of sovereign duke over a given territory or domain.
- 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_69d87f1a8dd881909f1de6ef78849874 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e20169ce488190bbc814f23a3b7547 |
completed | April 17, 2026, 9:46 a.m. |
| PD | Predicate disambiguation | batch_69e1828518c48190a8ef3aaa46a1f639 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 5 a.m.