Triple
T3165394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Katsina Emirate |
E66198
|
entity |
| Predicate | traditionalSuccession |
P8007
|
FINISHED |
| Object | hereditary rulership |
—
|
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 rulership | Statement: [Katsina Emirate, traditionalSuccession, hereditary rulership]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalSuccession Context triple: [Katsina Emirate, traditionalSuccession, hereditary rulership]
-
A.
successionRight
Indicates the legal or customary entitlement of one entity to inherit, assume, or take over the position, property, or role of another.
-
B.
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.
-
C.
successionOrder
Indicates the ordered sequence in which entities are designated to succeed or take over a role, position, or title.
-
D.
successorDynasty
Indicates that one dynasty directly follows and replaces another in a sequence of rule or authority.
-
E.
successionPattern
chosen
Indicates the characteristic way in which one entity follows, replaces, or is ordered after another in a sequence or succession.
- 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_69ad8585d7988190af37365331093ccd |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada6424ee48190a29891ffbbc3811d |
completed | March 8, 2026, 4:39 p.m. |
| PD | Predicate disambiguation | batch_69ad9dfe0a948190928f2201d671c654 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:06 p.m.