Triple
T25446604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kapiri Mposhi |
E637652
|
entity |
| Predicate | roadConnectsVia |
P9041
|
FINISHED |
| Object | Great North Road to Lusaka |
—
|
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: Great North Road to Lusaka | Statement: [Kapiri Mposhi, roadConnectsVia, Great North Road to Lusaka]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadConnectsVia Context triple: [Kapiri Mposhi, roadConnectsVia, Great North Road to Lusaka]
-
A.
ropewayConnects
Indicates that a ropeway (such as a cable car or gondola system) provides a direct transportation connection between two locations.
-
B.
roadConnectivityStatus
Indicates the current state of whether and how well two locations are connected by a road network.
-
C.
roadConnectionRegion
Indicates that a road provides a direct transportation connection between two regions.
-
D.
roadAccessVia
chosen
Indicates that one location or area is reachable from another specifically by using a particular road or road segment.
-
E.
roadJunctionIncludes
Indicates that a road junction spatially contains or encompasses a specific road segment or related roadway element as part of its structure.
- 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_69e75db7c5048190b8da9cd7eeedb610 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f70455f48190b23c09dbed884015 |
completed | May 2, 2026, 1:07 p.m. |
| PD | Predicate disambiguation | batch_69f4806d93dc8190b9dff4c63186faff |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 2:02 p.m.