Triple
T35498496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Highbrook |
E1025930
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | suburb of Auckland |
C64481
|
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: suburb of Auckland Context triple: [Highbrook, instanceOf, suburb of Auckland]
-
A.
suburb of Wellington
A suburb of Wellington is a residential or mixed-use area located within the greater Wellington metropolitan region, typically characterized by local amenities, community services, and transport links to the central city.
-
B.
suburb of Melbourne
A suburb of Melbourne is a defined residential or mixed-use area located within the greater Melbourne metropolitan region, characterized by its own local amenities, community identity, and governance under a local council.
-
C.
suburb district of Canberra
A suburb district of Canberra is a defined residential and mixed-use area within the Canberra metropolitan region, characterized by its own local amenities, community identity, and governance within the broader Australian Capital Territory.
-
D.
Suburb of Nairobi
A Suburb of Nairobi is a residential or mixed-use area located on the outskirts of Nairobi city, typically characterized by lower building density than the urban core and serving as a commuter or satellite community connected to the city’s economic and social activities.
-
E.
suburban centre
A suburban centre is a focal area within a suburb that concentrates retail, services, and community facilities, serving as a local hub for surrounding residential neighborhoods.
- F. None of above. chosen
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_69f76dfc9c60819089c4217d93922615 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:04 p.m.