Triple
T24618803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Logone-et-Chari Department |
E609345
|
entity |
| Predicate | sharesBorderAlongRiverWith |
P143613
|
FINISHED |
| Object | Chad |
—
|
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: Chad | Statement: [Logone-et-Chari Department, sharesBorderAlongRiverWith, Chad]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesBorderAlongRiverWith Context triple: [Logone-et-Chari Department, sharesBorderAlongRiverWith, Chad]
-
A.
borderedByCountryAcrossRiver
Indicates that one country shares a border with another country, with the boundary specifically formed or separated by a river.
-
B.
borderingWaters
Indicates that a geographic area directly touches or is adjacent to a particular body of water.
-
C.
countryBordering
Indicates that one country shares a land or maritime boundary directly with another country.
-
D.
borderedBy
Indicates that one entity shares a common boundary or edge with another entity.
-
E.
bordersAcrossRiver
chosen
Indicates that two regions or entities share a boundary with each other that is separated or defined by a river.
- 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_69e2c4d1140081909c58667bf68f80c3 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f2be044d4c819094e14eda28d371a7 |
completed | April 30, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f2a6ca751c8190a040c10d701ecf3a |
completed | April 30, 2026, 12:48 a.m. |
Created at: April 18, 2026, 2:32 a.m.