Triple

T22939898
Position Surface form Disambiguated ID Type / Status
Subject Northolt Underground station E569693 entity
Predicate stationCode P1289 FINISHED
Object NHT 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: NHT | Statement: [Northolt Underground station, stationCode, NHT]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: NHT
Context triple: [Northolt Underground station, stationCode, NHT]
  • A. NHT chosen
    NHT is the IATA airport code for RAF Northolt, a Royal Air Force station in West London that also handles some civil and governmental air traffic.
  • B. NHTO
    NHTO is the National Household Targeting Office, a government body responsible for identifying and prioritizing poor and vulnerable households for social protection programs.
  • C. HNT
    HNT is the station code used by the Long Island Rail Road for Huntington station in New York.
  • D. NH
    NH is an abbreviation commonly used in India to denote a National Highway within the country’s road network.
  • E. NH
    NH is the two-letter IATA airline designator assigned to All Nippon Airways, Japan’s largest airline.
  • 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_69e24590862c8190858f180ad302adab completed April 17, 2026, 2:37 p.m.
NER Named-entity recognition batch_69f1813844b88190b05d3829b0c423c4 completed April 29, 2026, 3:55 a.m.
Created at: April 17, 2026, 3:45 p.m.