Triple
T2583611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shango |
E57147
|
entity |
| Predicate | cultCenter |
P9995
|
FINISHED |
| Object | Oyo |
E276474
|
NE 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 | Statement: [Shango, cultCenter, Oyo]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Oyo Context triple: [Shango, cultCenter, Oyo]
-
A.
Oyo
Oyo is a prominent Yoruba subgroup historically known for its powerful Oyo Empire in what is now southwestern Nigeria.
-
B.
Oyo State
Oyo State is a southwestern Nigerian state historically known as the heartland of the old Oyo Empire and a major center of Yoruba culture and politics.
-
C.
Oyo-Ile
chosen
Oyo-Ile was the historic political and cultural center of the Oyo Empire, one of the most powerful precolonial Yoruba states in West Africa.
-
D.
Morvi State
Morvi State was a former princely state in western India, historically governed by the Jadeja Rajput dynasty.
-
E.
Tonk State
Tonk State was a princely state in British India, notable for being one of the few Muslim-ruled states in the largely Rajput-dominated region of present-day Rajasthan.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ab4a4dca6481908c301f8e317396e7 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd3cb33a08190a3eae1a95e1b63bf |
completed | March 7, 2026, 7:29 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69af657f39dc8190971e0ad7a5396257 |
completed | March 10, 2026, 12:27 a.m. |
Created at: March 6, 2026, 9:49 p.m.