Triple
T31297842
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zongo |
E798128
|
entity |
| Predicate | nearInternationalBorderWith |
P46305
|
FINISHED |
| Object | Central African Republic |
—
|
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: Central African Republic | Statement: [Zongo, nearInternationalBorderWith, Central African Republic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearInternationalBorderWith Context triple: [Zongo, nearInternationalBorderWith, Central African Republic]
-
A.
nearInternationalBoundary
chosen
Indicates that one entity is located close to an international boundary separating two or more countries.
-
B.
nearFormerBorderWith
Indicates that one entity is located close to where the former border or boundary with another entity used to be.
-
C.
nearBorderCrossing
Indicates that an entity is located close to a border crossing point between two regions or countries.
-
D.
connectsToCountryBorder
Indicates that one entity is directly adjacent to and touches the border of a specified country.
-
E.
nearStateBorderWith
Indicates that one entity is located close to the state border shared with another specified state or region.
- 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_69f224e0bd4c8190aab9b29a73f7aa3c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d1bf8cc8190a78dfa5ab00daf3a |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 9:14 p.m.