Triple
T14718292
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oba dynasty |
E345739
|
entity |
| Predicate | roleInNigeria |
P115509
|
FINISHED |
| Object | custodian of Benin culture |
—
|
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: custodian of Benin culture | Statement: [Oba dynasty, roleInNigeria, custodian of Benin culture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInNigeria Context triple: [Oba dynasty, roleInNigeria, custodian of Benin culture]
-
A.
roleInPhilippines
Indicates that an entity holds or has held an official or notable role, position, or function within the Philippines.
-
B.
roleInNepal
Indicates that an entity holds or has held a specific role, position, or function within the context of Nepal.
-
C.
roleInKuomboka
Indicates that an entity holds a specific role or function within the context of the Kuomboka ceremony or event.
-
D.
roleInPakistan
Indicates that an entity holds or has held a specific role, position, or function within the context of Pakistan.
-
E.
roleInBrazil
Indicates that an entity holds or held a specific role, position, or function within the context of Brazil.
- F. None of above. chosen
Provenance (4 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_69d822e5911c8190ba589f957dbd9ba7 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb98823408190b4b58a4c4a3fa3a3 |
completed | April 14, 2026, 10:02 p.m. |
| PD | Predicate disambiguation | batch_69de657e174481909da0437556334a04 |
completed | April 14, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69de716d3aac8190aaa6dc1f099b86e8 |
completed | April 14, 2026, 4:55 p.m. |
Created at: April 10, 2026, 1:29 a.m.