Triple
T25363412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boulgou Province |
E636034
|
entity |
| Predicate | hasKeyLocalCenter |
P18908
|
FINISHED |
| Object | Tenkodogo |
—
|
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: Tenkodogo | Statement: [Boulgou Province, hasKeyLocalCenter, Tenkodogo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeyLocalCenter Context triple: [Boulgou Province, hasKeyLocalCenter, Tenkodogo]
-
A.
hasKeyCenter
Indicates that one entity serves as the primary tonal or central pitch reference (key center) for another entity, such as a musical passage or composition.
-
B.
hasCenterIn
Indicates that something is located, based, or primarily focused within a specified central place or area.
-
C.
hasKeyPoint
Indicates that one entity includes, contains, or is associated with a specific key point or main idea represented by another entity.
-
D.
hasCenterFeature
Indicates that an entity possesses a specific feature or element located at its center.
-
E.
hasKeyLocation
chosen
Indicates that an entity possesses or is associated with a specific primary or important location relevant to it.
- 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_69e75a9b7cf481909f2dcdfb37d95ca7 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f638d11c988190af7fd4572b08e038 |
completed | May 2, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69f63706b6008190993577193c85ff50 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 21, 2026, 1:36 p.m.