Triple
T30183993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cyangugu |
E767282
|
entity |
| Predicate | hasBorderPostType |
P47626
|
FINISHED |
| Object | road border crossing |
—
|
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: road border crossing | Statement: [Cyangugu, hasBorderPostType, road border crossing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBorderPostType Context triple: [Cyangugu, hasBorderPostType, road border crossing]
-
A.
hasBorderPostWith
Indicates that two regions or territories share a border where an official border post or checkpoint is located between them.
-
B.
borderPostType
chosen
Indicates the specific kind or classification of a border post associated with a boundary or crossing point.
-
C.
borderPostIs
Indicates that one entity functions as a border post associated with or located at another entity.
-
D.
connectsToBorderPost
Indicates that one entity is linked or leads directly to a border post, establishing a route or connection between them.
-
E.
hasBorderFacilityType
Indicates that a border facility possesses or is classified by a specific type or category of border-related infrastructure or service.
- 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_69f2247cc3d88190811dec3face94bf5 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fccdd496048190bca801a8a9eecb62 |
completed | May 7, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69fcccee6240819084680887731ff64b |
completed | May 7, 2026, 5:33 p.m. |
Created at: April 29, 2026, 7:26 p.m.