Triple

T21422648
Position Surface form Disambiguated ID Type / Status
Subject HBG E528473 entity
Predicate hasAbbreviation P43 FINISHED
Object HBG 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: HBG | Statement: [HBG, hasAbbreviation, HBG]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: HBG
Context triple: [HBG, hasAbbreviation, HBG]
  • A. HBG chosen
    HBG is the station code for Hallonbergen metro station on the Stockholm Metro system in Sweden.
  • B. HBG
    HBG was a major Dutch construction and civil engineering company known for large-scale infrastructure and building projects in the Netherlands and abroad.
  • C. HGB
    HGB is the abbreviation for the German Commercial Code, the central body of law governing commercial transactions and business entities in Germany.
  • D. BHB
    BHB is the stock exchange of the Kingdom of Bahrain, providing a regulated marketplace for trading securities and other financial instruments.
  • E. HGF
    HGF is the abbreviation for the Helmholtz Association, Germany’s largest scientific research organization spanning multiple disciplines and large-scale facilities.
  • 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_69e0c455f3688190810bc96365791b0f completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69ee62d392e08190b7f378005afc9026 completed April 26, 2026, 7:09 p.m.
Created at: April 16, 2026, 5:48 p.m.