Triple

T21927703
Position Surface form Disambiguated ID Type / Status
Subject 26th Wisconsin Infantry Regiment E541483 entity
Predicate armyCorpsAssignment P61848 FINISHED
Object XX 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: XX Corps | Statement: [26th Wisconsin Infantry Regiment, armyCorpsAssignment, XX Corps]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: XX Corps
Context triple: [26th Wisconsin Infantry Regiment, armyCorpsAssignment, XX Corps]
  • A. XX Corps
    XX Corps was a British Army corps-level formation that served in the Middle Eastern theatre during the First World War, particularly in the Sinai and Palestine campaigns.
  • B. XX Corps chosen
    XX Corps was a U.S. Army corps-level formation best known for its combat operations in the European Theater during World War II.
  • C. XXXI Corps
    XXXI Corps is a major field formation of the Pakistan Army responsible for operational command and defense in its assigned region.
  • D. XXX Corps
    XXX Corps is a major field formation of the Pakistan Army responsible for operational command and defense in its assigned region.
  • E. XXX Corps
    XXX Corps was a British Army corps that played a significant role in several major operations during World War II, particularly in the Northwest Europe campaign.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69e0c47d74488190a15119108794a307 completed April 16, 2026, 11:14 a.m.
NER Named-entity recognition batch_69f123fc188481909c74fd5f1bd52258 completed April 28, 2026, 9:17 p.m.
Created at: April 16, 2026, 7:46 p.m.