Triple
T36681446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gaborone–Johannesburg route |
E905692
|
entity |
| Predicate | roadComponentUses |
P186163
|
FINISHED |
| Object | A1 road (Botswana) |
—
|
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: A1 road (Botswana) | Statement: [Gaborone–Johannesburg route, roadComponentUses, A1 road (Botswana)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadComponentUses Context triple: [Gaborone–Johannesburg route, roadComponentUses, A1 road (Botswana)]
-
A.
roadUse
Indicates that an entity utilizes or travels on a particular road or roadway for movement or transport.
-
B.
usedTransportationInfrastructure
Indicates that an entity made use of some form of transportation infrastructure (such as roads, railways, or ports) to enable movement or transit.
-
C.
roadBuiltFor
Indicates that a road was constructed specifically to serve, provide access to, or support the use or needs of a particular entity.
-
D.
hasRoadComponent
Indicates that something includes, contains, or is composed of a specific road-related part or element.
-
E.
roadNetworkPartOf
Indicates that one road network segment or component is a constituent part of a larger road network.
- 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_69f76e7011dc819082b324f18b756a1b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7c83f5960819089610ed39c839678 |
completed | May 3, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f7c4796ebc819084a0dc08505e5f14 |
completed | May 3, 2026, 9:56 p.m. |
| PDg | Predicate description generation | batch_69f7c776b4088190bef550c869da530d |
completed | May 3, 2026, 10:08 p.m. |
Created at: May 3, 2026, 4:12 p.m.