Triple

T9943387
Position Surface form Disambiguated ID Type / Status
Subject 69th Army E194138 entity
Predicate formedFrom P402 FINISHED
Object 28th Army E138145 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: 28th Army | Statement: [69th Army, formedFrom, 28th Army]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: 28th Army
Context triple: [69th Army, formedFrom, 28th Army]
  • A. 28th Army chosen
    The 28th Army was a field army of the Soviet Red Army that fought on the Eastern Front during World War II, participating in major operations against Nazi Germany.
  • B. 27th Army
    The 27th Army was a field army of the Soviet Red Army that fought on the Eastern Front during World War II, participating in major offensives under various Soviet fronts.
  • C. 23rd Army
    The 23rd Army was a field army of the Soviet Red Army that took part in major Eastern Front operations during World War II, particularly in the Soviet–Finnish conflicts.
  • D. 64th Army
    The 64th Army was a Soviet Red Army field formation that played a key role in the defense and counteroffensive at the Battle of Stalingrad during World War II.
  • E. 43rd Army
    The 43rd Army was a field army of the Soviet Red Army that fought on the Eastern Front during World War II, participating in major operations including the advance through Belarus and into East Prussia.
  • 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_69ca82e409348190a393777356b80a2a completed March 30, 2026, 2:04 p.m.
NER Named-entity recognition batch_69cdb6124a188190b41feadb7b2f8922 completed April 2, 2026, 12:19 a.m.
NED1 Entity disambiguation (via context triple) batch_69d2291a22f88190acf055a7410c1808 completed April 5, 2026, 9:19 a.m.
Created at: March 30, 2026, 8:45 p.m.