Triple
T36427009
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Downtown Woodstock |
E897328
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | neighbourhood of Woodstock, Ontario |
C19774
|
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: neighbourhood of Woodstock, Ontario Context triple: [Downtown Woodstock, instanceOf, neighbourhood of Woodstock, Ontario]
-
A.
neighbourhood of Hamilton, Ontario
A neighbourhood of Hamilton, Ontario is a distinct residential or mixed-use area within the city characterized by its own local identity, land use patterns, community amenities, and social and physical boundaries.
-
B.
neighbourhood in Mississauga
A neighbourhood in Mississauga is a defined residential area within the city characterized by its local amenities, community services, housing types, and distinct social and cultural identity.
-
C.
neighbourhood in Ottawa
A neighbourhood in Ottawa is a defined residential and mixed-use area within the city characterized by its local community, amenities, and distinct geographic or cultural identity.
-
D.
subregion of Ontario
chosen
A subregion of Ontario is a defined geographic area within the province characterized by shared administrative, economic, cultural, or environmental features that distinguish it from other parts of Ontario.
-
E.
neighborhood in Montreal
A neighborhood in Montreal is a distinct urban area within the city characterized by its own mix of residential and commercial spaces, cultural identity, language influences, and local amenities that reflect Montreal’s diverse heritage.
- 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_69f76e559b10819099d6655a6e14587c |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:10 p.m.