Triple

T5180370
Position Surface form Disambiguated ID Type / Status
Subject 35th Infantry Division E116903 entity
Predicate higherCommand P1407 FINISHED
Object XIX Corps E456685 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: XIX Corps | Statement: [35th Infantry Division, higherCommand, XIX Corps]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: XIX Corps
Context triple: [35th Infantry Division, higherCommand, XIX Corps]
  • A. XIX Corps chosen
    XIX Corps was a U.S. Army corps-level formation that saw significant combat in the European Theater during World War II, particularly in the Normandy campaign and subsequent operations across France and Germany.
  • B. XV Corps
    XV Corps was a field corps of the Ottoman Army that served as a major combat formation during World War I.
  • C. XV Corps
    XV Corps is a key field formation of the Indian Army responsible for military operations and security in the Kashmir region.
  • D. XVI Corps
    XVI Corps was a field corps of the Ottoman Army that served on multiple fronts during World War I, including the Gallipoli and Caucasus campaigns.
  • E. XVI Corps
    XVI Corps is a major field formation of the Indian Army responsible for military operations in parts of the northern region of India.
  • 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_69bd446140f08190becb93c61158f27f completed March 20, 2026, 12:58 p.m.
NER Named-entity recognition batch_69bd799a322c8190b8a590cfe70761f5 completed March 20, 2026, 4:45 p.m.
NED1 Entity disambiguation (via context triple) batch_69befe5521dc8190b2c6f03faa436529 completed March 21, 2026, 8:23 p.m.
Created at: March 20, 2026, 1:45 p.m.