Triple
T17163745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bénouville Bridge |
E416551
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | World War II historical site |
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 historical site Context triple: [Bénouville Bridge, instanceOf, World War II historical site]
-
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-era state
A World War II-era state is a sovereign political entity operating between roughly 1933 and 1945 whose institutions, economy, military, and society were shaped by the global conflict, wartime alliances, and total war mobilization.
-
C.
World War I site
A World War I site is a historically significant location directly associated with events, operations, or impacts of the First World War, such as battlefields, trenches, memorials, cemeteries, or military installations.
-
D.
Cold War military site
A Cold War military site is a strategically located facility, installation, or complex developed or used during the Cold War era for defense, surveillance, weapons deployment, command and control, or related military operations shaped by nuclear deterrence and superpower rivalry.
-
E.
World War II event
A World War II event is a historically significant occurrence between 1939 and 1945 that directly influenced the political, military, social, or economic course of the global conflict.
- 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_69d886d279c081909f8ff1f743ddeb69 |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:37 a.m.