Triple
T9218924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | D-Day landing area |
E221310
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military geographic region |
C16458
|
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 geographic region Context triple: [D-Day landing area, instanceOf, military geographic region]
-
A.
geographical region
A geographical region is a defined area of the Earth's surface characterized by shared physical, cultural, political, or environmental features that distinguish it from surrounding areas.
-
B.
Geographic combatant command
A geographic combatant command is a unified military command responsible for planning and conducting operations within a specific, defined region of the world.
-
C.
physical region
A physical region is a bounded area of space characterized by specific physical properties, conditions, or features that distinguish it from surrounding areas.
-
D.
military administrative division
A military administrative division is a geographically defined area organized under a specific command structure to manage, coordinate, and support military operations, logistics, and governance within its boundaries.
-
E.
military-controlled zone
chosen
A military-controlled zone is a designated geographic area where military authorities exercise primary control over security, movement, and activities, often restricting civilian access and enforcing special regulations.
- 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_69ca83eae42c8190a0ea9e040710a277 |
completed | March 30, 2026, 2:08 p.m. |
Created at: March 30, 2026, 7:27 p.m.