Triple
T23469181
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ekiti State Secretariat |
E569178
|
entity |
| Predicate | capitalOfServedEntity |
P106647
|
FINISHED |
| Object | Ekiti State |
—
|
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: Ekiti State | Statement: [Ekiti State Secretariat, capitalOfServedEntity, Ekiti State]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capitalOfServedEntity Context triple: [Ekiti State Secretariat, capitalOfServedEntity, Ekiti State]
-
A.
capitalOfContainingEntity
chosen
Indicates that one entity serves as the capital city or administrative center of another, larger containing entity (such as a country, state, or region).
-
B.
capitalOfRuledEntity
Indicates that a city or settlement serves as the capital of a political entity that rules or governs another entity.
-
C.
countryCapitalOfRegionServed
Indicates that a country is the capital or primary governing center of the specified region it serves.
-
D.
capitalOfCountryServed
Indicates that a city serves as the capital of a given country.
-
E.
capitalOftenLocatedIn
Indicates that the capital city of a region or country is frequently, though not always, situated within a particular location or type of area.
- 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_69e2458ebd808190b3298163132cfb0b |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a6feb5688190ad4ce42fc9590adb |
completed | April 29, 2026, 6:36 a.m. |
| PD | Predicate disambiguation | batch_69f06201d33481909b5fd7b92d03e658 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 5:54 p.m.