Triple
T24109556
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arkady Gaidar |
E597327
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Red Army veteran |
C48281
|
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: Red Army veteran Context triple: [Arkady Gaidar, instanceOf, Red Army veteran]
-
A.
Polish–Ukrainian War veteran
A Polish–Ukrainian War veteran is an individual who served as a combatant or military participant in the conflict between Poland and the West Ukrainian People's Republic from 1918 to 1919.
-
B.
Red Army commander
A Red Army commander is a high-ranking military officer responsible for planning, directing, and overseeing Soviet armed forces operations and personnel within the Red Army.
-
C.
World War II veteran
A World War II veteran is an individual who served in the armed forces of any nation during the global conflict of 1939–1945, participating in military operations or support roles related to the war.
-
D.
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.
-
E.
Russian field marshal
A Russian field marshal is the highest-ranking military officer in the Russian (historically Imperial or Soviet-equivalent) army, responsible for commanding large-scale operations and shaping overall military strategy.
- 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_69e288c60f9c8190af948d7354aedbeb |
completed | April 17, 2026, 7:23 p.m. |
Created at: April 17, 2026, 11:02 p.m.