Triple
T36230478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gbêkê Region |
E891227
|
entity |
| Predicate | prominentCity |
P50537
|
FINISHED |
| Object | Bouaké |
—
|
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: Bouaké | Statement: [Gbêkê Region, prominentCity, Bouaké]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: prominentCity Context triple: [Gbêkê Region, prominentCity, Bouaké]
-
A.
primaryCity
Indicates that one city serves as the main or most important city associated with a given region, entity, or context.
-
B.
principalCityOf
chosen
Indicates that a city serves as the main or most important city (often administrative, economic, or cultural center) of a specified region or area.
-
C.
cityPromoted
Indicates that an entity (such as an organization, person, or campaign) carried out promotional activities to advertise or raise the profile of a particular city.
-
D.
cityOn
Indicates that a city is geographically located on a specified landform, area, or administrative region.
-
E.
otherMajorCity
Indicates that one city is another major city associated with or comparable in importance or status to the first city.
- 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_69f76e4387048190a1b27bcbf4ec7423 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bcccd7988190aa5c931ff347d33c |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:09 p.m.