Triple
T25740416
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baron Sumption, of Mount Harry in the County of East Sussex |
E648199
|
entity |
| Predicate | hasNoHeirs |
P179894
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Baron Sumption, of Mount Harry in the County of East Sussex, hasNoHeirs, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNoHeirs Context triple: [Baron Sumption, of Mount Harry in the County of East Sussex, hasNoHeirs, true]
-
A.
hadNoLegitimateHeirs
Indicates that the person died without any legally recognized offspring who could inherit their title, property, or rights.
-
B.
hadNoSurvivingChildren
Indicates that the person did not have any children who were alive at the relevant point in time.
-
C.
hasNoAutomaticSuccessionRight
Indicates that an entity does not possess an inherent or legally recognized right to automatically succeed another entity in a role, position, or entitlement.
-
D.
hasDeceasedParent
Indicates that an entity has at least one parent who is no longer living.
-
E.
hasNoLegitimateChildren
chosen
Indicates that the subject does not have any children who are legally recognized as legitimate.
- 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_69e7ab306eec8190b05c312c6ab186b8 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f791cc969c8190bf187d6031a030d5 |
completed | May 3, 2026, 6:19 p.m. |
| PD | Predicate disambiguation | batch_69f791033d288190b118029fe412b9c9 |
completed | May 3, 2026, 6:16 p.m. |
Created at: April 22, 2026, 3:42 a.m.