Triple
T36933264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | County of Banff |
E913541
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic local government area |
C11688
|
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: historic local government area Context triple: [County of Banff, instanceOf, historic local government area]
-
A.
historic subdistrict
A historic subdistrict is a geographically defined area within a larger district that contains a concentration of buildings, structures, or sites recognized for their historical, architectural, or cultural significance and is subject to preservation guidelines or protections.
-
B.
historic township
chosen
A historic township is a former or long-established local administrative or geographic subdivision, often with distinct historical boundaries, governance, and community identity that may differ from modern municipal structures.
-
C.
historic locality
A historic locality is a geographically defined place recognized for its significant past events, cultural heritage, or historical importance.
-
D.
historic region
A historic region is a geographically defined area recognized for its significant past events, cultural heritage, or historical identity that has shaped its development over time.
-
E.
historic ward
A historic ward is an administrative or electoral subdivision of a city or town that has maintained its traditional boundaries, identity, and often architectural character from a significant period in the past.
- 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_69f76e896c988190880c130e01303dd4 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:13 p.m.