Triple
T35157915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ohunbe |
E1015178
|
entity |
| Predicate | hasAdministrativeCapitalState |
P6344
|
FINISHED |
| Object | Abeokuta |
—
|
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: Abeokuta | Statement: [Ohunbe, hasAdministrativeCapitalState, Abeokuta]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAdministrativeCapitalState Context triple: [Ohunbe, hasAdministrativeCapitalState, Abeokuta]
-
A.
hasCapitalAdministered
Indicates that a specified capital city is responsible for administering or governing a particular territory or political entity.
-
B.
isStateCapital
chosen
Indicates that a city serves as the official capital of a given state.
-
C.
isDistrictCapitalOf
Indicates that a location serves as the administrative or governmental capital of a specified district.
-
D.
isLegislativeCapitalOf
Indicates that a location serves as the primary seat of a region’s legislative branch or lawmaking body.
-
E.
governingTerritorialCapital
Indicates that a territorial entity serves as the administrative or political capital for a governing body or jurisdiction.
- 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_69f76ddb3a708190b521ba2970b17178 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fddf721c1481909301a0f379368f10 |
completed | May 8, 2026, 1:04 p.m. |
| PD | Predicate disambiguation | batch_69fddda1ae7c8190b5848ff9a9e39826 |
completed | May 8, 2026, 12:57 p.m. |
Created at: May 3, 2026, 4:02 p.m.