Triple
T294549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York and New Jersey campaign |
E6064
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | American Revolutionary War campaign |
C340
|
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: American Revolutionary War campaign Context triple: [New York and New Jersey campaign, instanceOf, American Revolutionary War campaign]
-
A.
military campaign phase
A military campaign phase is a distinct, time-bounded segment of a broader military operation characterized by specific objectives, actions, and resource allocations that contribute to the overall strategic goal.
-
B.
World War II campaign
A World War II campaign is a coordinated series of military operations conducted over a specific period and geographic area, aimed at achieving strategic objectives within the broader context of the war.
-
C.
military operation
chosen
A military operation is a coordinated and planned set of actions conducted by armed forces to achieve specific strategic, operational, or tactical objectives.
-
D.
battles
Battles are organized, often large-scale armed conflicts between opposing forces, characterized by strategic maneuvers, tactical engagements, and the pursuit of specific military objectives within a defined time and place.
-
E.
event in the War of 1812
An "event in the War of 1812" is a specific historical occurrence—such as a battle, treaty, political decision, or military campaign—that took place between 1812 and 1815 and directly relates to the conflict between the United States, the United Kingdom, and their respective allies.
- 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_69a2e79114b081909490b3bf5a5dbb51 |
completed | Feb. 28, 2026, 1:03 p.m. |
Created at: Feb. 28, 2026, 1:06 p.m.