Triple
T14664795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bamako–Dakar Railway |
E344338
|
entity |
| Predicate | hasBorderTerminusCountry |
P115255
|
FINISHED |
| Object | landlocked country |
—
|
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: landlocked country | Statement: [Bamako–Dakar Railway, hasBorderTerminusCountry, landlocked country]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBorderTerminusCountry Context triple: [Bamako–Dakar Railway, hasBorderTerminusCountry, landlocked country]
-
A.
hasBorderWithinCountry
Indicates that one region or area shares an internal boundary with another region or area within the same country.
-
B.
hasBorderMeetingCountry
Indicates that one country shares a land or maritime border with another country.
-
C.
hasBorderTerminus
Indicates that one entity serves as the endpoint or terminal location of another entity’s border or boundary.
-
D.
hasBorderPostWith
Indicates that two regions or territories share a border where an official border post or checkpoint is located between them.
-
E.
borderTerminus
Indicates the endpoint location where a border between two areas or entities begins or ends.
- F. None of above. chosen
Provenance (4 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_69d822e283fc8190a0e4c235cf880052 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb54c69f8819080a37161deecfba8 |
completed | April 14, 2026, 9:44 p.m. |
| PD | Predicate disambiguation | batch_69de6576f0208190aa94d995e797ac38 |
completed | April 14, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69de716c17cc8190aeb85296abee85a7 |
completed | April 14, 2026, 4:55 p.m. |
Created at: April 10, 2026, 1:27 a.m.