Triple
T37047206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern Dagaare |
E916948
|
entity |
| Predicate | neighboringRegionsOfUse |
P17964
|
FINISHED |
| Object | border areas near Burkina Faso |
—
|
LITERAL FINISHED |
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: border areas near Burkina Faso | Statement: [Southern Dagaare, neighboringRegionsOfUse, border areas near Burkina Faso]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: neighboringRegionsOfUse Context triple: [Southern Dagaare, neighboringRegionsOfUse, border areas near Burkina Faso]
-
A.
networkRegion
Indicates that an entity belongs to, operates within, or is associated with a specific network-defined geographic or logical region.
-
B.
neighboringRegion
chosen
Indicates that two regions share a common boundary or are directly adjacent to each other geographically.
-
C.
neighboringProvision
Indicates that one entity provides resources, services, or support to another entity located nearby or in an adjacent area.
-
D.
regionalNeighbor
Indicates that two regions share a common boundary or are directly adjacent to each other geographically.
-
E.
telecomRegime
Indicates a regulatory or governance framework that defines how telecommunications services are organized, controlled, and operated within a given context.
- 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_69f76e94d0308190a3f06890e133c88e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb55de3b9c8190a7656aeab3c3ffbc |
completed | May 6, 2026, 2:53 p.m. |
| PD | Predicate disambiguation | batch_69fb35bc92e08190bff447624e2df791 |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:14 p.m.