Triple
T34770589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Allied order of battle in Normandy |
E1002352
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical military structure |
C2458
|
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: historical military structure Context triple: [Allied order of battle in Normandy, instanceOf, historical military structure]
-
A.
military structure
A military structure is an organized framework of ranks, units, and command relationships that defines how armed forces are arranged, governed, and coordinated to conduct operations.
-
B.
historical armed forces
chosen
Historical armed forces are organized military institutions from past eras, composed of soldiers, equipment, and command structures, created by states or societies to conduct warfare, defend territories, and project power.
-
C.
military administrative structure
A military administrative structure is the organized system of offices, roles, procedures, and chains of command that manage the planning, support, and governance of armed forces.
-
D.
19th-century military structure
A 19th-century military structure is a fortified installation or facility designed and built during the 1800s to support, protect, and organize armed forces, often reflecting the era’s evolving technologies, tactics, and geopolitical needs.
-
E.
World War II-era military structure
A World War II-era military structure is a fortified or purpose-built facility—such as bunkers, command posts, airfields, or coastal defenses—designed to support, protect, and coordinate military operations during the Second World War.
- 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_69f76db20dac8190b1e8d0ca4dc1d59f |
completed | May 3, 2026, 3:45 p.m. |
Created at: May 3, 2026, 3:59 p.m.