Triple
T21462024
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Czechoslovak paratroopers |
E529495
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Czechoslovak military unit |
C20739
|
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: Czechoslovak military unit Context triple: [Czechoslovak paratroopers, instanceOf, Czechoslovak military unit]
-
A.
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.
-
B.
Czechoslovak paratrooper
chosen
A Czechoslovak paratrooper is a specially trained airborne soldier from former Czechoslovakia, prepared to deploy by parachute behind enemy lines for reconnaissance, sabotage, and rapid assault operations.
-
C.
Freikorps unit
A Freikorps unit is a semi-autonomous, often nationalist paramilitary formation composed largely of ex-soldiers, operating with limited state oversight in post–World War I Germany to combat perceived internal and external enemies.
-
D.
Polish military contingent
A Polish military contingent is a temporary, organized group of Polish Armed Forces personnel and resources deployed for specific missions, operations, or international commitments.
-
E.
Czechoslovak legionnaire
A Czechoslovak legionnaire is a member of the volunteer military units formed by Czechs and Slovaks during World War I (and shortly after) who fought alongside the Allies to secure independence from Austria-Hungary and helped lay the foundations of Czechoslovakia.
- 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_69e0c458133481908ae8b41a12c4edec |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:09 p.m.