Triple

T17798919
Position Surface form Disambiguated ID Type / Status
Subject I Corps (Republic of Korea) E444367 entity
Predicate nickname P55 FINISHED
Object I 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: I Corps | Statement: [I Corps (Republic of Korea), nickname, I Corps]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: I Corps
Context triple: [I Corps (Republic of Korea), nickname, I Corps]
  • A. I Corps
    I Corps is a major U.S. Army corps-level headquarters responsible for commanding and coordinating large-scale land operations, with a primary focus on the Indo-Pacific region.
  • B. I Corps
    I Corps was a major British Army field formation that played key roles in both World Wars, particularly in early operations in France and Belgium.
  • C. I Corps chosen
    I Corps is a major field corps-level formation of the Republic of Korea Army responsible for operational command and control of multiple divisions.
  • D. I Corps
    I Corps was a major French military formation of the Armée du Nord, notably active during the Napoleonic Wars.
  • E. I Corps
    I Corps is a major field formation of the Pakistan Army responsible for conducting large-scale offensive and defensive operations.
  • 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_69d8b9efe370819095cd219b143ae727 completed April 10, 2026, 8:50 a.m.
NER Named-entity recognition batch_69e487fcfdc8819086f41152860dfe18 completed April 19, 2026, 7:45 a.m.
Created at: April 10, 2026, 10:13 a.m.