Triple
T1395418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | General Commander of the Branches of the Armed Forces |
E30654
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Polish military position |
C6538
|
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 military position Context triple: [General Commander of the Branches of the Armed Forces, instanceOf, Polish military position]
-
A.
Polish military history event
A Polish military history event is a significant occurrence involving Poland’s armed forces—such as battles, campaigns, uprisings, operations, or strategic decisions—that influenced the course of Poland’s national or military development.
-
B.
NATO military position
A NATO military position is a standardized role or appointment within the North Atlantic Treaty Organization’s integrated command or force structure, defining specific responsibilities, rank equivalencies, and functions across member nations’ armed forces.
-
C.
British Army position
A British Army position is a specific role or rank within the British Army’s organizational structure, defining an individual’s responsibilities, authority, and place in the military hierarchy.
-
D.
military occupation
A military occupation is the effective control and administration of a territory by foreign armed forces without the sovereign consent of the territory’s recognized government.
-
E.
military unit
A military unit is an organized group of armed personnel structured under a defined command hierarchy to perform specific tactical or operational missions.
- 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_69a498fd4e408190bd73eca30ea9754c |
completed | March 1, 2026, 7:52 p.m. |
Created at: March 1, 2026, 7:59 p.m.