Triple
T36215997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oranmiyan |
E1047695
|
entity |
| Predicate | successorAsDynasticAncestor |
P124532
|
FINISHED |
| Object | Oyo royal lineage |
—
|
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: Oyo royal lineage | Statement: [Oranmiyan, successorAsDynasticAncestor, Oyo royal lineage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorAsDynasticAncestor Context triple: [Oranmiyan, successorAsDynasticAncestor, Oyo royal lineage]
-
A.
predecessorInDynasticLine
Indicates that one entity held a dynastic position or title before another in the same hereditary succession line.
-
B.
successorDynastyOrigin
Indicates the place or cultural-geographic origin from which a successor dynasty arises in relation to its predecessor.
-
C.
successorDynasticContext
chosen
Indicates that one entity becomes the next holder of power, title, or position in a dynastic or hereditary succession context.
-
D.
successorDynasty
Indicates that one dynasty directly follows and replaces another in a sequence of rule or authority.
-
E.
resultedInSuccessionFrom
Indicates that one entity’s outcome or event directly caused or led to the succession or replacement of 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_69f76e4214748190a76c986d2a1838c2 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a0059f4ffe481908dc500cee9051148 |
completed | May 10, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_6a00593a3c1881909b2ff1a29eb474b3 |
completed | May 10, 2026, 10:08 a.m. |
Created at: May 3, 2026, 4:09 p.m.