Triple
T9598997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polish High Command |
E231802
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Polish military institution |
C26815
|
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 institution Context triple: [Polish High Command, instanceOf, Polish military institution]
-
A.
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.
-
B.
Belgian military institution
A Belgian military institution is an organization within Belgium’s defense structure responsible for training, organizing, and supporting the country’s armed forces in accordance with national and international security objectives.
-
C.
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.
-
D.
Finnish military formation
A Finnish military formation is an organized grouping of Finnish Defence Forces personnel and equipment, structured at various hierarchical levels (such as squad, platoon, company, battalion, brigade, or higher) to conduct coordinated military operations.
-
E.
Polish military decoration
A Polish military decoration is an official honor awarded by the Polish state to recognize acts of bravery, merit, or distinguished service in military or related national defense activities.
- 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_69ca8484838c8190b2049199d22fef70 |
completed | March 30, 2026, 2:11 p.m. |
Created at: March 30, 2026, 8:07 p.m.