Triple
T30719508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Biton Coulibaly |
E782111
|
entity |
| Predicate | capitalFoundedOrUsed |
P3417
|
FINISHED |
| Object | Ségou |
—
|
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: Ségou | Statement: [Biton Coulibaly, capitalFoundedOrUsed, Ségou]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capitalFoundedOrUsed Context triple: [Biton Coulibaly, capitalFoundedOrUsed, Ségou]
-
A.
capitalCityEstablished
Indicates that a particular city was officially designated or founded as the capital of a political or administrative entity.
-
B.
capitalCityBuildingOf
Indicates that a building is located in and associated with the capital city of a given political or administrative entity.
-
C.
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.
-
D.
capitalLocation
Indicates the relationship in which a place serves as the capital city or administrative center of a given political or geographic entity.
-
E.
formerCapitalOf
chosen
Indicates that a place once served as the capital of another entity (such as a country or region) but no longer holds that status.
- 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_69f224acd24481908ed5f96f0d69b5dd |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fba78aca4c8190b8f1831e8cc04e06 |
completed | May 6, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69fba34a65a4819088bac6c17542d71c |
completed | May 6, 2026, 8:23 p.m. |
Created at: April 29, 2026, 8:36 p.m.