Triple
T17577795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Region D (City of Johannesburg) |
E428116
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | subdivision of City of Johannesburg Metropolitan Municipality |
C34587
|
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: subdivision of City of Johannesburg Metropolitan Municipality Context triple: [Region D (City of Johannesburg), instanceOf, subdivision of City of Johannesburg Metropolitan Municipality]
-
A.
subregion of Gauteng
A subregion of Gauteng is a defined geographic or administrative area within the Gauteng province, used for organizing governance, planning, or statistical analysis.
-
B.
subdivision of district
A subdivision of district is an administrative unit that forms a smaller, constituent part of a larger district within a governmental or organizational hierarchy.
-
C.
Municipality of South Africa
A Municipality of South Africa is a local government administrative division responsible for providing basic services, infrastructure, and governance within a defined urban or rural area of the country.
-
D.
region of Cape Town
A region of Cape Town is a geographically defined area within the city’s metropolitan boundary, characterized by shared administrative governance, infrastructure, and socio-economic and cultural features.
-
E.
subdivision
chosen
A subdivision is a defined portion of a larger area or entity that has been divided into smaller, distinct parts for organizational, administrative, or functional purposes.
- 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_69d889e0385081908a04b66f4dd4bd0d |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:50 a.m.