Triple

T23168741
Position Surface form Disambiguated ID Type / Status
Subject HMDC E578784 entity
Predicate abbreviation P43 FINISHED
Object HMDC 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: HMDC | Statement: [HMDC, abbreviation, HMDC]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: HMDC
Context triple: [HMDC, abbreviation, HMDC]
  • A. HMDC chosen
    HMDC is the Hibernia Management and Development Company, the consortium responsible for managing and developing the Hibernia offshore oil field off the coast of Newfoundland and Labrador, Canada.
  • B. DHM
    DHM is the National Rail station code for Durham railway station in County Durham, England.
  • C. DHM
    DHM is the commonly used abbreviation for the German Historical Museum in Berlin, a major institution dedicated to documenting and presenting German history.
  • D. DHM
    DHM is the IATA airport code for Kangra Airport, a regional airport serving Dharamshala and the surrounding Kangra Valley in Himachal Pradesh, India.
  • E. HdM
    HdM is the commonly used abbreviation for Stuttgart Media University, a German university specializing in media, information, and communication studies.
  • 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_69e245fc75348190a0288401044c8af8 completed April 17, 2026, 2:38 p.m.
NER Named-entity recognition batch_69f18f2e5e208190839ec37de4b974af completed April 29, 2026, 4:55 a.m.
Created at: April 17, 2026, 4:03 p.m.