Triple
T30741701
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baronet |
E782707
|
entity |
| Predicate | typicalSuccessionRule |
P171639
|
FINISHED |
| Object | male primogeniture |
—
|
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: male primogeniture | Statement: [Baronet, typicalSuccessionRule, male primogeniture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalSuccessionRule Context triple: [Baronet, typicalSuccessionRule, male primogeniture]
-
A.
successionPattern
Indicates the characteristic way in which one entity follows, replaces, or is ordered after another in a sequence or succession.
-
B.
usedSuccessionSystem
chosen
Indicates that an entity employed a particular system or method for determining succession or inheritance of position, title, or authority.
-
C.
governedSuccessionOf
Indicates a succession relationship in which one entity follows another under an established governing rule, law, or authority.
-
D.
successionDefinedBy
Indicates that the rules, order, or conditions of succession for one entity are determined or specified by another entity.
-
E.
successionNature
Indicates the type or manner of succession by which one entity follows or replaces another (e.g., hereditary, elective, or otherwise).
- 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_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e2fac0819089b522db3260028c |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 8:38 p.m.