Triple

T22872550
Position Surface form Disambiguated ID Type / Status
Subject Military Region II E567236 entity
Predicate alsoKnownAs P39 FINISHED
Object II Corps NE NERFINISHED

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: II Corps | Statement: [Military Region II, alsoKnownAs, II Corps]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: II Corps
Context triple: [Military Region II, alsoKnownAs, II Corps]
  • A. II Corps
    II Corps was a major field formation of the Ottoman Army that played a significant role in several key campaigns during World War I.
  • B. II Corps
    II Corps was a major field formation of the British Army that saw significant service in both World War I and World War II.
  • C. II Corps
    II Corps is a major field formation of the Pakistan Army, headquartered in Multan and responsible for key operational and defensive roles along Pakistan’s eastern front.
  • D. II Corps
    II Corps is a major field formation of the Republic of Korea Army, historically active in key operations during the Korean War and responsible for commanding multiple divisions in its area of responsibility.
  • E. II Corps
    II Corps was a major Union Army corps in the American Civil War, renowned for its pivotal role and heavy engagement in key Eastern Theater battles such as Antietam, Chancellorsville, and Gettysburg.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide. 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_69e24589d8348190b96422d13a678bc1 completed April 17, 2026, 2:36 p.m.
NER Named-entity recognition batch_69f17f55c4b88190adb49871e496ca54 completed April 29, 2026, 3:47 a.m.
Created at: April 17, 2026, 3:38 p.m.