Triple

T21804460
Position Surface form Disambiguated ID Type / Status
Subject InterCity 125 E538314 entity
Predicate alsoKnownAs P39 FINISHED
Object HST 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: HST | Statement: [InterCity 125, alsoKnownAs, HST]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: HST
Context triple: [InterCity 125, alsoKnownAs, HST]
  • A. HST
    HST is the FAA airport code for Homestead Air Reserve Base, a United States Air Force installation in Florida.
  • B. HST chosen
    HST is a high-speed passenger train designed to operate at significantly higher speeds than conventional rail services, often used for rapid intercity travel.
  • C. HST
    HST is the vehicle registration code used on license plates for the district of Vorpommern-Rügen in the German state of Mecklenburg-Vorpommern.
  • D. HST
    HST is a collaborative Harvard–MIT program that integrates medicine, engineering, and science to advance education and research in health sciences and technology.
  • E. HST
    HST is the station code used to identify Hornstull metro station in the Stockholm Metro system.
  • 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_69e0c4733f4081909a86622e7e6d15d2 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69f07801fa8081909098d00947bf8f7f completed April 28, 2026, 9:04 a.m.
Created at: April 16, 2026, 6:53 p.m.