Triple
T26694009
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battles and operations of the Eastern Front of World War II |
E672969
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military campaign collection |
C3442
|
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: military campaign collection Context triple: [Battles and operations of the Eastern Front of World War II, instanceOf, military campaign collection]
-
A.
military formation collection
A military formation collection is an organized set of multiple military units or formations grouped together for coordinated command, maneuver, and operational effectiveness.
-
B.
military campaign theater
chosen
A military campaign theater is a geographically defined area where coordinated military operations and strategies are conducted to achieve specific objectives within a broader conflict.
-
C.
air assault campaign
An air assault campaign is a coordinated series of military operations that use rotary- and tilt-rotor aircraft to rapidly insert, support, and extract ground forces in contested or hostile areas to achieve specific tactical or operational objectives.
-
D.
military campaign streamer
A military campaign streamer is a ribbon-like cloth attachment affixed to a military unit's flag or guidon that denotes participation in and honors earned during a specific campaign or operation.
-
E.
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.
- 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_69eecda2066c8190a344218afa5e89c1 |
completed | April 27, 2026, 2:44 a.m. |
Created at: April 27, 2026, 3:27 a.m.