Triple
T10565400
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lake Champlain campaign |
E249336
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | War of 1812 campaign |
C18479
|
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: War of 1812 campaign Context triple: [Lake Champlain campaign, instanceOf, War of 1812 campaign]
-
A.
battle of the Northwest Indian War
A battle of the Northwest Indian War is an armed military engagement between United States forces and a coalition of Native American nations fought in the Old Northwest between 1785 and 1795 as part of the struggle for control of the region.
-
B.
War of 1812 participant
chosen
A War of 1812 participant is an individual, military unit, or entity that took part in the military, political, or support activities associated with the War of 1812 between the United States, the British Empire, and their respective allies.
-
C.
Native American war
A Native American war is an armed conflict involving Indigenous peoples of the Americas, often fought to defend their lands, resources, sovereignty, and cultural survival against other Native groups or external powers.
-
D.
civil war battle
A civil war battle is an armed conflict between organized factions within the same country, typically involving large-scale military engagements over political, territorial, or ideological control.
-
E.
Apache Wars engagement
An Apache Wars engagement is a specific military confrontation or skirmish between Apache groups and opposing forces (such as U.S. or Mexican military or settlers) during the broader series of conflicts known as the Apache Wars.
- 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_69d381c8bd708190acf3d275c908251e |
completed | April 6, 2026, 9:50 a.m. |
Created at: April 6, 2026, 12:36 p.m.