Triple
T30918226
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bemowo Piskie military training area |
E787644
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Polish Army training ground |
C59566
|
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: Polish Army training ground Context triple: [Bemowo Piskie military training area, instanceOf, Polish Army training ground]
-
A.
Canadian Army training centre
A Canadian Army training centre is a military facility where Canadian Army personnel receive instruction, practice, and evaluation in the skills, tactics, and procedures required for operational readiness and professional development.
-
B.
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.
-
C.
Bulgarian Army facility
A Bulgarian Army facility is a military installation in Bulgaria used by the Bulgarian Armed Forces for operations, training, logistics, administration, or support activities.
-
D.
United States Army training range
A United States Army training range is a designated area equipped and managed for conducting military training exercises, weapons qualification, and tactical simulations under controlled and safe conditions.
-
E.
former military training camp
A former military training camp is a decommissioned facility once used to prepare armed forces personnel through drills, exercises, and instruction, now repurposed, abandoned, or preserved for historical or alternative uses.
- F. None of above. chosen
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_69f224bfaca88190b9d0dfcc86297fe9 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:51 p.m.