Triple
T38400504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | History of Quebec |
E900884
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | history of a Canadian province |
C61028
|
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: history of a Canadian province Context triple: [History of Quebec, instanceOf, history of a Canadian province]
-
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.
province of Canada
A province of Canada is a primary administrative division of the country with its own government, legislature, and constitutional powers distinct from the federal government.
-
C.
era in Canadian history
An era in Canadian history is a distinct period characterized by particular political, social, economic, and cultural developments that significantly shape the nation’s identity and trajectory.
-
D.
province of British North America
A province of British North America was a colonial administrative division under British rule in North America prior to Canadian Confederation, encompassing territories such as Upper Canada, Lower Canada, Nova Scotia, and others.
-
E.
Canadian history work
chosen
A Canadian history work is a scholarly or educational creation—such as a book, article, documentary, or exhibit—that examines, interprets, or presents events, people, and developments from Canada’s 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_69f76e6071a081909eea7a670d21420c |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:31 p.m.