Triple

T19192144
Position Surface form Disambiguated ID Type / Status
Subject 52nd Army E469865 entity
Predicate subordinateTo P258 FINISHED
Object Reserve of the Supreme High Command NE NERFINISHED

How this triple was built (3 steps)

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.

NER Named-entity recognition gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Reserve of the Supreme High Command | Statement: [52nd Army, subordinateTo, Reserve of the Supreme High Command]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Reserve of the Supreme High Command
Context triple: [52nd Army, subordinateTo, Reserve of the Supreme High Command]
  • A. High Command of the Armed Forces
    The High Command of the Armed Forces was Nazi Germany’s supreme military command authority overseeing the coordination and strategic direction of the Wehrmacht during World War II.
  • B. General Command of the Military Forces
    The General Command of the Military Forces is the highest operational and strategic leadership body overseeing Colombia’s Army, Navy, and Air Force.
  • C. Ministry of Defense of the USSR
    The Ministry of Defense of the USSR was the central government body responsible for directing and administering the Soviet Union’s armed forces and overall military policy.
  • D. Military Collegium of the Supreme Court of the USSR
    The Military Collegium of the Supreme Court of the USSR was a high-level Soviet judicial body that handled serious criminal and political cases involving military personnel and state security matters.
  • E. People's Commissar for Defence of the USSR
    The People's Commissar for Defence of the USSR was the top Soviet government post responsible for directing the Red Army and overseeing the military defense policy of the Soviet Union.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07
Target entity: Reserve of the Supreme High Command
Target entity description: The Reserve of the Supreme High Command was a strategic pool of Soviet military formations in World War II, held under direct control of the highest command for rapid deployment to critical sectors of the front.
  • A. High Command of the Armed Forces
    The High Command of the Armed Forces was Nazi Germany’s supreme military command authority overseeing the coordination and strategic direction of the Wehrmacht during World War II.
  • B. General Command of the Military Forces
    The General Command of the Military Forces is the highest operational and strategic leadership body overseeing Colombia’s Army, Navy, and Air Force.
  • C. Ministry of Defense of the USSR
    The Ministry of Defense of the USSR was the central government body responsible for directing and administering the Soviet Union’s armed forces and overall military policy.
  • D. Military Collegium of the Supreme Court of the USSR
    The Military Collegium of the Supreme Court of the USSR was a high-level Soviet judicial body that handled serious criminal and political cases involving military personnel and state security matters.
  • E. People's Commissar for Defence of the USSR
    The People's Commissar for Defence of the USSR was the top Soviet government post responsible for directing the Red Army and overseeing the military defense policy of the Soviet Union.
  • F. None of above. chosen

Provenance (2 batches)

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_69d8dd0ad9088190a173b32657ae2e7a completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5f8a3434881908acc4063a9ee9386 completed April 20, 2026, 9:57 a.m.
Created at: April 10, 2026, 12:07 p.m.