Triple
T17801252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alois Eliáš |
E444431
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Czechoslovak legionnaire |
C39168
|
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 legionnaire Context triple: [Alois Eliáš, instanceOf, Czechoslovak legionnaire]
-
A.
Slovak military officer
A Slovak military officer is a commissioned member of Slovakia’s armed forces responsible for leading personnel, planning and executing military operations, and upholding national defense and security policies.
-
B.
Czechoslovak paratrooper
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.
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.
Czech general
A Czech general is a high-ranking military officer from the Czech Republic responsible for leading armed forces, formulating defense strategies, and overseeing military operations and personnel.
-
E.
Austro-Hungarian military officer
An Austro-Hungarian military officer was a commissioned leader in the armed forces of the Austro-Hungarian Empire, responsible for commanding troops, implementing imperial military policy, and upholding the dual monarchy’s authority across its diverse territories.
- 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_69d8b9efe370819095cd219b143ae727 |
completed | April 10, 2026, 8:50 a.m. |
Created at: April 10, 2026, 10:13 a.m.