Triple

T9729241
Position Surface form Disambiguated ID Type / Status
Subject 10. Armee E235695 entity
Predicate alsoKnownAs P39 FINISHED
Object 10th Army E45698 NE FINISHED

How this triple was built (2 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: 10th Army | Statement: [10. Armee, alsoKnownAs, 10th Army]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: 10th Army
Context triple: [10. Armee, alsoKnownAs, 10th Army]
  • A. 10th Army chosen
    The 10th Army was a major German Wehrmacht field army that played a key role in early World War II campaigns, including the invasion of Poland.
  • B. 10th Army
    The 10th Army was a Soviet Red Army field formation that played a major role on the Eastern Front during the early stages of World War II.
  • C. 5th Army
    The 5th Army was a major field army of the Soviet Red Army that played a significant role on the Eastern Front during World War II, particularly in operations conducted by the 3rd Belorussian Front.
  • D. 66th Army
    The 66th Army was a Soviet Red Army field formation in World War II that played a key role in the Battle of Stalingrad before later being redesignated as the 5th Guards Army.
  • E. 6th Army
    The 6th Army was a major German Wehrmacht field army in World War II, best known for its encirclement and destruction at the Battle of Stalingrad.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 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_69ca84d0fad481909cdd45aa77416c48 completed March 30, 2026, 2:12 p.m.
NER Named-entity recognition batch_69cd9eafa3a88190bc62924d94b89cd8 completed April 1, 2026, 10:39 p.m.
NED1 Entity disambiguation (via context triple) batch_69d1bcc8d2288190b2a1dc3fe1185030 completed April 5, 2026, 1:37 a.m.
Created at: March 30, 2026, 8:21 p.m.