Triple
T15894630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gian Gastone de' Medici |
E385420
|
entity |
| Predicate | reasonForDynasticEnd |
P110086
|
FINISHED |
| Object | died without legitimate 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: died without legitimate heirs | Statement: [Gian Gastone de' Medici, reasonForDynasticEnd, died without legitimate heirs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForDynasticEnd Context triple: [Gian Gastone de' Medici, reasonForDynasticEnd, died without legitimate heirs]
-
A.
dynastyEndedWith
Indicates that a particular dynasty concluded or came to an end with the specified ruler, event, or time period.
-
B.
endOfReignReason
Indicates the cause or circumstance that led to the termination of a ruler’s reign.
-
C.
dynasticOutcome
Indicates the result or consequence of a succession or transfer of power within a dynasty, such as continuation, change, or end of a ruling line.
-
D.
extinctDynasty
chosen
Indicates that a dynasty has ceased to exist and no longer continues through ruling descendants or recognized lineage.
-
E.
dynasticOrigin
Indicates the historical dynasty or ruling family from which an entity originates or descends.
- 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_69d86da5b800819083a31be937d738b0 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e17d4d08f481909f38b75e3f42d9ab |
completed | April 17, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69e142ca3b208190946c3aa4c1e6087c |
completed | April 16, 2026, 8:12 p.m. |
Created at: April 10, 2026, 4:51 a.m.