Triple
T8754863
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand Dérangement |
E208048
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Acadian history event |
C383
|
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: Acadian history event Context triple: [Grand Dérangement, instanceOf, Acadian history event]
-
A.
Acadian culture
Acadian culture is the distinct French-speaking heritage of the Acadian people, shaped by early colonial settlement in Atlantic Canada, the trauma of the Great Expulsion, and a resilient tradition of music, cuisine, language, and community life that persists in regions like New Brunswick, Nova Scotia, Prince Edward Island, and Louisiana.
-
B.
colonial-era event
chosen
A colonial-era event is a historically significant occurrence that took place during a period when one nation exercised political, economic, or cultural control over foreign territories and populations.
-
C.
Hawaiian history event
A Hawaiian history event is a significant occurrence in the past of the Hawaiian Islands that shaped their political, cultural, social, or environmental development.
-
D.
Revolutionary War event
A Revolutionary War event is a significant occurrence—such as a battle, political decision, treaty, or social upheaval—that directly influenced the course, conduct, or outcome of the American Revolutionary War.
-
E.
event in King George's War
An event in King George's War is a specific military, political, or diplomatic occurrence between 1744 and 1748 that contributed to the course and outcome of the conflict between Britain and France in North America and Europe.
- 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_69ca835cd6b08190bd7c63db92f53c86 |
completed | March 30, 2026, 2:06 p.m. |
Created at: March 30, 2026, 6:39 p.m.