Triple
T17297748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Task Force White Eagle |
E419956
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Polish military contingent |
C39038
|
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 contingent Context triple: [Task Force White Eagle, instanceOf, Polish military contingent]
-
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.
Polish–Lithuanian Commonwealth military personnel
Individuals who served in the armed forces of the Polish–Lithuanian Commonwealth, including its army, navy, and related military formations, from its formation in 1569 until its final partitions in the late 18th century.
-
C.
Czechoslovak exile unit
A Czechoslovak exile unit is a military formation composed of Czechoslovak personnel organized outside their occupied homeland, typically under foreign command, to continue armed resistance or fulfill allied military roles.
-
D.
Polish Air Force unit
A Polish Air Force unit is an organizational entity within Poland’s air arm responsible for operating, maintaining, and supporting assigned aircraft and air defense systems to fulfill national defense and allied mission objectives.
-
E.
Polish military institution
A Polish military institution is an organization established by the Polish state to manage, train, support, or command elements of the armed forces in accordance with national defense policies and legal frameworks.
- 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_69d886db32608190a61e18862c5a8af6 |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:41 a.m.