Triple
T15352689
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commander of the 1st Far Eastern Front |
E367091
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Red Army command position |
C35960
|
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 command position Context triple: [Commander of the 1st Far Eastern Front, instanceOf, Red Army command position]
-
A.
Luftwaffe command position
A Luftwaffe command position is an organizational role within the German air force hierarchy responsible for directing air operations, managing resources, and implementing strategic and tactical decisions.
-
B.
Wehrmacht headquarters
The Wehrmacht headquarters was the central command authority of Nazi Germany's unified armed forces, responsible for strategic planning, coordination, and direction of military operations during World War II.
-
C.
Wehrmacht position
A Wehrmacht position is a designated location or role within the German armed forces of Nazi Germany during World War II, encompassing specific duties, rank, and tactical responsibilities in military operations.
-
D.
army commander post
An army commander post is a designated command facility or position from which a military commander directs, coordinates, and controls the operations of assigned forces.
-
E.
command-and-control facility
A command-and-control facility is a secure, centralized location equipped with communication, monitoring, and decision-support systems used to direct and coordinate operations and resources in real time.
- 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_69d85a1355608190a6673ddb67231d54 |
completed | April 10, 2026, 2:01 a.m. |
Created at: April 10, 2026, 3:17 a.m.