Triple

T6243210
Position Surface form Disambiguated ID Type / Status
Subject Eastern Command E139652 entity
Predicate hasComponent P35 FINISHED
Object IV Corps E368617 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: IV Corps | Statement: [Eastern Command, hasComponent, IV Corps]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: IV Corps
Context triple: [Eastern Command, hasComponent, IV Corps]
  • A. IV Corps chosen
    IV Corps was a British Army corps-level formation that played a significant role on the Western Front during World War I.
  • B. I Corps
    I Corps is a major field corps-level formation of the Republic of Korea Army responsible for operational command and control of multiple divisions.
  • C. 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.
  • D. 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.
  • E. I Corps
    I Corps was a major field formation of the Ottoman Army that played a significant role in the empire’s military operations during the First World War.
  • 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_69c008b1c5088190ae6de2555fc05ad8 completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c0631b32308190a8211043d1caa6e6 completed March 22, 2026, 9:46 p.m.
NED1 Entity disambiguation (via context triple) batch_69c24406809c8190a827a52abce88ecc completed March 24, 2026, 7:57 a.m.
Created at: March 22, 2026, 4:23 p.m.