Triple
T7389650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Military history of New France |
E170467
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | history of New France |
C9499
|
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 New France Context triple: [Military history of New France, instanceOf, history of New France]
-
A.
military commander in New France
A military commander in New France was a royal appointee responsible for organizing, leading, and coordinating French colonial troops and allied Indigenous forces to defend and expand the colony’s territories in North America.
-
B.
former French colony
A former French colony is a territory that was once governed or administered by France as part of its overseas empire but has since gained independence or undergone a change in political status.
-
C.
Dutch–Native American conflict
Dutch–Native American conflict refers to the series of violent and diplomatic confrontations between Dutch colonists and Indigenous peoples in North America during the 17th century, driven by competition over land, trade, and political control.
-
D.
European colonists
European colonists were settlers from various European nations who migrated to and established control over foreign lands, often displacing indigenous populations and exploiting local resources for economic and political gain.
-
E.
historical topic
chosen
A historical topic is a specific subject, event, period, or theme from the past that is studied, analyzed, and interpreted to understand historical developments and their impact.
- 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_69c68a5e2c9081909e713ce866e0060a |
completed | March 27, 2026, 1:47 p.m. |
Created at: March 27, 2026, 3:09 p.m.