Triple
T7291171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | František Moravec |
E164395
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Czechoslovak military officer |
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 officer Context triple: [František Moravec, instanceOf, Czechoslovak military officer]
-
A.
Yugoslav military officer
A Yugoslav military officer is a commissioned member of the armed forces of the former Socialist Federal Republic of Yugoslavia, responsible for leading troops, planning and executing military operations, and upholding the doctrines and political-military objectives of the Yugoslav state.
-
B.
Polish military leader
A Polish military leader is a high-ranking commander from Poland responsible for planning, directing, and overseeing military operations and the strategic use of armed forces in defense of the nation.
-
C.
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.
-
D.
Austrian general
An Austrian general is a high-ranking military officer from Austria responsible for planning, directing, and overseeing large-scale military operations and strategic defense initiatives.
-
E.
Serbian general
A Serbian general is a high-ranking military officer from Serbia responsible for leading and commanding large military formations, planning operations, and shaping national defense strategy.
- 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_69c6887a499881909dd23341399c59d8 |
completed | March 27, 2026, 1:39 p.m. |
Created at: March 27, 2026, 3 p.m.