Triple
T35025436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ota Awori Kingdom |
E1010321
|
entity |
| Predicate | chieftaincyHierarchy |
P120851
|
FINISHED |
| Object | Olota as paramount ruler |
—
|
NE NERFINISHED |
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: Olota as paramount ruler | Statement: [Ota Awori Kingdom, chieftaincyHierarchy, Olota as paramount ruler]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chieftaincyHierarchy Context triple: [Ota Awori Kingdom, chieftaincyHierarchy, Olota as paramount ruler]
-
A.
clanChiefBranchOf
Indicates that a particular clan chief belongs to, or is a leading figure within, a specific branch or subdivision of a larger clan.
-
B.
hasChieftaincyStructure
chosen
Indicates that an entity possesses an organized system of traditional leadership or chieftaincy hierarchy.
-
C.
clanChiefRank
Indicates that the subject holds the rank or position of chief within a clan in relation to the object.
-
D.
hasChiefClan
Indicates that one entity serves as the primary or leading clan associated with another entity.
-
E.
clanChiefRecognition
Indicates that an individual is formally acknowledged or endorsed as a chief by a particular clan or its traditional 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_69f76dccf0108190af43b465d3750196 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78ce78b508190955848e133398dc8 |
completed | May 3, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69f78b8f4cc08190b49fccd798cb25d7 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4:01 p.m.