Triple
T30741727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baronet |
E782707
|
entity |
| Predicate | successionOnDeath |
P71549
|
FINISHED |
| Object | eldest legitimate son |
—
|
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: eldest legitimate son | Statement: [Baronet, successionOnDeath, eldest legitimate son]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successionOnDeath Context triple: [Baronet, successionOnDeath, eldest legitimate son]
-
A.
successionOutcome
Indicates the result or consequence of a succession event, such as who or what ultimately assumes a position, role, or status after a predecessor.
-
B.
successionRight
Indicates the legal or customary entitlement of one entity to inherit, assume, or take over the position, property, or role of another.
-
C.
successionNote
Indicates that there is a note or annotation describing details or context about a succession relationship between entities.
-
D.
successionBasis
chosen
Indicates the legal or customary basis on which one entity succeeds or takes over from another in a position, role, or title.
-
E.
successionOrder
Indicates the ordered sequence in which entities are designated to succeed or take over a role, position, or title.
- 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_69f224aeb1588190897d395e8ed2acb8 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fea2d0a4d08190aa06aeb902a02d5a |
completed | May 9, 2026, 2:58 a.m. |
| PD | Predicate disambiguation | batch_69fea24698348190b9b992a8e7cdbcd0 |
completed | May 9, 2026, 2:56 a.m. |
Created at: April 29, 2026, 8:38 p.m.