Triple
T11804850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King |
E280718
|
entity |
| Predicate | typicalSuccessionMode |
P8007
|
FINISHED |
| Object | hereditary succession |
—
|
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: hereditary succession | Statement: [King, typicalSuccessionMode, hereditary succession]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalSuccessionMode Context triple: [King, typicalSuccessionMode, hereditary succession]
-
A.
successorRegimeType
Indicates the type or form of government or regime that directly follows and replaces a preceding regime.
-
B.
successionPattern
chosen
Indicates the characteristic way in which one entity follows, replaces, or is ordered after another in a sequence or succession.
-
C.
supportedSuccessionOf
Indicates that one entity actively endorsed or helped bring about the transfer of power, position, or role from a predecessor to a successor.
-
D.
successorType
Indicates the specific kind or category of successor relationship that holds between one entity and the next in a sequence or hierarchy.
-
E.
governedSuccessionOf
Indicates a succession relationship in which one entity follows another under an established governing rule, law, or authority.
- 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_69d6ab26aae88190b2489efcb2a24234 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a658f918819092c2db05fe2ab0ce |
completed | April 10, 2026, 7:27 a.m. |
| PD | Predicate disambiguation | batch_69d8a24e9a088190aff7932d1ff93dbf |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:42 p.m.