Triple
T10014390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Sforza |
E199449
|
entity |
| Predicate | extinctionOfDucalLine |
P48008
|
FINISHED |
| Object | 1535 |
—
|
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: 1535 | Statement: [House of Sforza, extinctionOfDucalLine, 1535]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: extinctionOfDucalLine Context triple: [House of Sforza, extinctionOfDucalLine, 1535]
-
A.
successorInAngevinLine
Indicates that one entity is the next holder of a title, position, or role in the Angevin lineage directly following another entity.
-
B.
successorAsLancastrianHeir
Indicates that one entity becomes the next recognized heir in the Lancastrian line of succession after another entity.
-
C.
extinctionOfMaleLine
chosen
Indicates that a family’s direct male lineage has ended, with no surviving male descendants to continue it.
-
D.
reasonForEndOfBritishLine
Indicates the cause or circumstance that led to the termination or extinction of a particular British lineage or line.
-
E.
dynasticClaim
Indicates a relationship where one party asserts a hereditary or lineage-based right to rule, inherit, or hold authority over another.
- 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_69ca8315a1a08190ab310f25620f362b |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cdcd49b19c8190b429e3533d072648 |
completed | April 2, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69cd4b7cd4208190b2253583ee2f892c |
completed | April 1, 2026, 4:44 p.m. |
Created at: March 30, 2026, 8:52 p.m.