Triple

T7919500
Position Surface form Disambiguated ID Type / Status
Subject HCDN E183909 entity
Predicate usesAbbreviation P43 FINISHED
Object HCDN E183909 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: HCDN | Statement: [HCDN, usesAbbreviation, HCDN]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: HCDN
Context triple: [HCDN, usesAbbreviation, HCDN]
  • A. HCDN chosen
    HCDN is the commonly used abbreviation for the Chamber of Deputies, the lower house of Argentina’s National Congress.
  • B. CDN
    CDN is the ICAO airline designator formerly assigned to Canadian Airlines, a major now-defunct Canadian carrier.
  • C. HCD
    HCD is the California state agency responsible for housing policy, affordable housing programs, and community development initiatives.
  • D. Hdn
    Hdn is the station code for Handen station, a commuter rail stop in the Stockholm County region of Sweden.
  • E. DHCD
    DHCD is the commonly used abbreviation for the Maryland Department of Housing and Community Development, the state agency responsible for housing policy, community revitalization, and related support programs in Maryland.
  • 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_69ca828efbe48190bd48482650182e79 completed March 30, 2026, 2:02 p.m.
NER Named-entity recognition batch_69cb3a9173548190a04889726f7b251f completed March 31, 2026, 3:08 a.m.
NED1 Entity disambiguation (via context triple) batch_69cb5beea7988190972f7d02881d98f6 completed March 31, 2026, 5:30 a.m.
Created at: March 30, 2026, 5:05 p.m.