Triple
T26749205
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cavalaire landing sector |
E674485
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | World War II landing zone |
C702
|
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: World War II landing zone Context triple: [Cavalaire landing sector, instanceOf, World War II landing zone]
-
A.
World War II site
chosen
A World War II site is a historically significant location directly associated with events, operations, or impacts of the Second World War, preserved or recognized for its cultural, military, or memorial value.
-
B.
World War II prison
A World War II prison is a secured facility used during the war to detain military personnel, political prisoners, resistance members, and civilians under harsh and often inhumane conditions.
-
C.
World War II supply line
A World War II supply line is the network of transportation routes, logistics operations, and support infrastructure used to move troops, equipment, fuel, and provisions to and from battlefronts during the war.
-
D.
World War II commando raid
A World War II commando raid is a small-scale, highly planned military operation conducted by specially trained troops to infiltrate enemy territory, achieve a specific tactical or strategic objective, and withdraw quickly, often relying on surprise and stealth.
-
E.
World War II rear area
A World War II rear area is the zone behind the front lines where military forces organized logistics, supply, administration, medical care, training, and security operations to support combat units at the front.
- 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_69eecda63a3881908095c47900692e65 |
completed | April 27, 2026, 2:44 a.m. |
Created at: April 27, 2026, 3:52 a.m.