Triple

T22363888
Position Surface form Disambiguated ID Type / Status
Subject Historical Manuscripts Commission E552850 entity
Predicate alsoKnownAs P39 FINISHED
Object HMC 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: HMC | Statement: [Historical Manuscripts Commission, alsoKnownAs, HMC]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: HMC
Context triple: [Historical Manuscripts Commission, alsoKnownAs, HMC]
  • A. HMC
    HMC is a professional association of leading independent school heads in the United Kingdom and internationally.
  • B. HMC
    HMC is the stock ticker symbol for Honda Motor Co., Ltd., a major Japanese multinational manufacturer of automobiles, motorcycles, and power equipment.
  • C. HMC chosen
    HMC is the commonly used abbreviation for the Historical Manuscripts Commission, a former UK body responsible for surveying and advising on the preservation of historical archives and manuscripts.
  • D. HMC
    HMC is the commonly used abbreviation for Sheridan College’s Hazel McCallion Campus in Mississauga, Ontario.
  • E. HMC
    HMC is IBM’s Hardware Management Console, a specialized system used to configure, monitor, and manage IBM enterprise server hardware.
  • 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_69e11e4affcc8190ba7c27d29062558d completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f157d616748190921bd49039b7f6fc completed April 29, 2026, 12:59 a.m.
Created at: April 16, 2026, 8:44 p.m.