Triple
T14713767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deji of Akure |
E345621
|
entity |
| Predicate | roleInLocalGovernance |
P81461
|
FINISHED |
| Object | traditional authority |
—
|
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: traditional authority | Statement: [Deji of Akure, roleInLocalGovernance, traditional authority]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInLocalGovernance Context triple: [Deji of Akure, roleInLocalGovernance, traditional authority]
-
A.
urbanPolicyRole
Indicates a role or responsibility that an entity has in shaping, implementing, or influencing urban policy.
-
B.
cityGovernment
Indicates that a city’s governing authority has jurisdiction, control, or administrative responsibility over the referenced entity.
-
C.
hasLocalGovernanceRole
chosen
Indicates that an entity holds an official position or responsibility within a local or municipal governing body.
-
D.
councilParticipation
Indicates that an entity takes part in, or is a member of, a council or governing body.
-
E.
localPolity
Indicates that an entity is a governing body or political authority with jurisdiction over a specific local area or community.
- 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_69d822e4a8c08190a155df736bb7bc13 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb98513b081908b230f6ac79c72ad |
completed | April 14, 2026, 10:02 p.m. |
| PD | Predicate disambiguation | batch_69de657c57ec8190ae0b9bb79a514566 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:29 a.m.