Triple
T27813341
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colonial Canada |
E702592
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | era in Canadian history |
C53391
|
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: era in Canadian history Context triple: [Colonial Canada, instanceOf, era in Canadian history]
-
A.
Canadian historical entity
A Canadian historical entity is any past or present organization, institution, government body, or significant collective in Canada that has played a notable role in shaping the country’s social, political, economic, or cultural development.
-
B.
era in United States history
An era in United States history is a distinct time period characterized by particular political, social, economic, and cultural conditions or transformative events that differentiate it from other periods.
-
C.
era in Russian history
An era in Russian history is a distinct period characterized by specific political structures, social dynamics, cultural developments, and major events that collectively differentiate it from other periods in the nation’s past.
-
D.
Canadian cultural icon
A Canadian cultural icon is a person, symbol, place, or creation widely recognized as representing and shaping Canada’s national identity, values, and heritage.
-
E.
era in Swedish history
An era in Swedish history is a distinct period characterized by specific political structures, social conditions, cultural developments, and economic patterns that together define a recognizable phase in Sweden’s historical timeline.
- 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_69ef840a16748190926719ab96120bae |
completed | April 27, 2026, 3:43 p.m. |
Created at: April 27, 2026, 5:43 p.m.