Triple
T21911516
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Montreal (1844–1849) |
E541075
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical city status |
C45505
|
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: historical city status Context triple: [Montreal (1844–1849), instanceOf, historical city status]
-
A.
historic city-state
A historic city-state is an independent, self-governing urban center and its surrounding territory that functioned as a sovereign political, economic, and cultural entity in a specific historical period.
-
B.
historical city period
A historical city period is a span of time in a city's past characterized by distinctive social, political, economic, and cultural conditions that shape its development and identity.
-
C.
history of a city
A history of a city is a chronological account that traces the city’s origins, development, key events, and transformations over time, highlighting the social, political, economic, and cultural forces that shaped it.
-
D.
prefectural-level city (historical)
A prefectural-level city (historical) is an administrative division that historically combined an urban center with its surrounding rural areas under a single prefecture-level government, often serving as a regional political, economic, and cultural hub.
-
E.
historic urban center
A historic urban center is a densely built core area of a city characterized by its preserved architectural heritage, traditional street patterns, and long-standing cultural, social, and economic significance.
- 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_69e0c47c4b9c8190a5586a75f5f36453 |
completed | April 16, 2026, 11:14 a.m. |
Created at: April 16, 2026, 7:41 p.m.