Triple
T10653845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M1 motorway (Johannesburg) |
E251038
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | road in Johannesburg |
C20428
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: road in Johannesburg Context triple: [M1 motorway (Johannesburg), instanceOf, road in Johannesburg]
-
A.
road in South Africa
chosen
A road in South Africa is a constructed transportation route, ranging from national highways to local streets, designed to support vehicular and pedestrian movement while adhering to the country’s specific traffic laws, signage standards, and infrastructural conditions.
-
B.
road in Shanghai
A road in Shanghai is a transportation corridor within the city’s dense urban fabric that supports mixed traffic—vehicles, buses, bicycles, and pedestrians—while integrating local infrastructure, commercial activity, and municipal regulations specific to Shanghai.
-
C.
road in Dubai
A road in Dubai is a modern, well-maintained transportation route designed to support high traffic volumes, integrate with advanced infrastructure, and connect key urban, commercial, and tourist areas across the city.
-
D.
road in Japan
A road in Japan is a public or private paved or unpaved route designed for vehicular and pedestrian travel, characterized by Japan-specific regulations, signage, and infrastructure standards.
-
E.
road in Brasília
A road in Brasília is a planned vehicular and pedestrian circulation route that follows the city’s modernist, superquadra-based urban design, organizing traffic flow and connecting residential, commercial, and civic sectors.
- F. None of above.
Provenance (1 batch)
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_69d6aa5a4c4881908f39be6efe5981e5 |
completed | April 8, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:06 p.m.