Triple
T8542481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shona states |
E202229
|
entity |
| Predicate | successionSystem |
P545
|
FINISHED |
| Object | hereditary monarchy |
—
|
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 monarchy | Statement: [Shona states, successionSystem, hereditary monarchy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successionSystem Context triple: [Shona states, successionSystem, hereditary monarchy]
-
A.
successionOrder
Indicates the ordered sequence in which entities are designated to succeed or take over a role, position, or title.
-
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.
successionInfluence
Indicates that one entity affects, shapes, or determines the succession or inheritance of another entity.
-
D.
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.
-
E.
successionDefinedBy
chosen
Indicates that the rules, order, or conditions of succession for one entity are determined or specified by another entity.
- 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_69ca832461e88190a654c5e44e233aa8 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe6e26be48190b10bc62fad178dad |
completed | March 31, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69cbd111bf988190be98c92a607c6456 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:18 p.m.