Triple
T9440162
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ostriv Zmiinyi |
E227622
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | strategic military location |
C14140
|
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: strategic military location Context triple: [Ostriv Zmiinyi, instanceOf, strategic military location]
-
A.
strategic maritime location
chosen
A strategic maritime location is a geographically significant sea area, chokepoint, or coastal zone whose control or access provides substantial military, economic, or logistical advantages in maritime operations and trade.
-
B.
military fortification system
A military fortification system is an integrated network of defensive structures, obstacles, and support facilities designed to protect territory, forces, and strategic assets from enemy attack.
-
C.
military installation
A military installation is a designated facility or area where armed forces are stationed, trained, equipped, and supported to conduct defense and security operations.
-
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.
Polish military position
A Polish military position is an organized role or rank within Poland's armed forces, defined by specific duties, authority, and responsibilities in the national defense structure.
- 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_69ca843884488190ad6cbe0153088234 |
completed | March 30, 2026, 2:10 p.m. |
Created at: March 30, 2026, 7:50 p.m.