Triple

T6299518
Position Surface form Disambiguated ID Type / Status
Subject Southern Command E141216 entity
Predicate hasUnit P35 FINISHED
Object 21 Corps E587883 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: 21 Corps | Statement: [Southern Command, hasUnit, 21 Corps]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: 21 Corps
Context triple: [Southern Command, hasUnit, 21 Corps]
  • A. XIX Corps
    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. XXIV Corps
    XXIV Corps was a U.S. Army corps-level formation that saw major combat in the Pacific Theater during World War II, including the Battle of Okinawa.
  • C. XV Corps
    XV Corps was a field corps of the Ottoman Army that served as a major combat formation during World War I.
  • D. XV Corps
    XV Corps is a key field formation of the Indian Army responsible for military operations and security in the Kashmir region.
  • E. XII Corps chosen
    XII Corps is a field formation of the Indian Army responsible for operations and defense in parts of western India, including sectors along the border with Pakistan.
  • 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_69c008cf0ad4819095def81e2bd42f9f completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c0645a7e048190af7a609fc74b876a completed March 22, 2026, 9:51 p.m.
NED1 Entity disambiguation (via context triple) batch_69c640aa8b608190ab834e77613f5218 completed March 27, 2026, 8:32 a.m.
Created at: March 22, 2026, 4:27 p.m.