Triple
T33471879
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ASF Bobo-Dioulasso |
E857213
|
entity |
| Predicate | isFromCityInCountry |
P70992
|
FINISHED |
| Object | Bobo-Dioulasso, Burkina Faso |
—
|
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: Bobo-Dioulasso, Burkina Faso | Statement: [ASF Bobo-Dioulasso, isFromCityInCountry, Bobo-Dioulasso, Burkina Faso]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFromCityInCountry Context triple: [ASF Bobo-Dioulasso, isFromCityInCountry, Bobo-Dioulasso, Burkina Faso]
-
A.
isInCity
Indicates that one entity is located within the geographical boundaries of a specified city.
-
B.
isInSameCityAs
Indicates that two entities are located within the boundaries of the same city.
-
C.
isCityOf
chosen
Indicates that one entity is a city that belongs to, is located within, or is administratively part of another entity (such as a country, state, or region).
-
D.
isInCountryISO
Indicates that one entity is located within, or belongs to, the country identified by a specific ISO country code.
-
E.
isSetInCountry
Indicates that something (such as an event, story, or scene) takes place within the geographical or political boundaries of a specified country.
- 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_69f3497472508190b300ebd3fd402367 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f96badb08190994442c2aba840b1 |
completed | May 3, 2026, 7:29 a.m. |
Created at: May 1, 2026, 1:37 a.m.