Triple

T18256289
Position Surface form Disambiguated ID Type / Status
Subject Hackage E437229 entity
Predicate associatedWith P37 FINISHED
Object GHC 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: GHC | Statement: [Hackage, associatedWith, GHC]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: GHC
Context triple: [Hackage, associatedWith, GHC]
  • A. GHC chosen
    GHC (Glasgow Haskell Compiler) is the most widely used, feature-rich, and optimizing compiler for the Haskell programming language.
  • B. GHC
    GHC is a leading international membership organization that advocates for improved global health policies and supports collaboration among health professionals, NGOs, and other stakeholders worldwide.
  • C. GHC
    GHC is the stock ticker symbol for Graham Holdings Company, a diversified American conglomerate with interests in education, media, and other businesses.
  • D. GHC
    GHC is the Gauhati High Court, the principal judicial authority for the Indian state of Assam and certain neighboring states in the Northeast region.
  • E. Haskell
    Haskell is a small town in Muskogee County, Oklahoma, known for its rural character and local community life.
  • 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_69d8b913351c8190932b6a426de04b41 completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e4fd85ee548190a102611fcf709ad4 completed April 19, 2026, 4:06 p.m.
Created at: April 10, 2026, 10:34 a.m.