Triple

T17613185
Position Surface form Disambiguated ID Type / Status
Subject Telarah railway station E429012 entity
Predicate hasStationCode P1289 FINISHED
Object TLH 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: TLH | Statement: [Telarah railway station, hasStationCode, TLH]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: TLH
Context triple: [Telarah railway station, hasStationCode, TLH]
  • A. TLH chosen
    TLH is the IATA airport code for Tallahassee International Airport, the primary commercial airport serving Florida’s state capital.
  • B. THL
    THL is the Finnish Institute for Health and Welfare, a national expert agency responsible for research, development, and guidance on public health and social welfare in Finland.
  • C. THLCH
    THLCH is the UN/LOCODE identifier for the major deep-sea commercial port of Laem Chabang in Thailand.
  • D. TLG
    TLG is the abbreviation for the Technical Liaison Group, a coordinating body that facilitates communication and collaboration among various technical standards organizations.
  • E. TLK
    TLK is a category of long-distance passenger trains in Poland operated by PKP Intercity, typically offering budget-friendly intercity connections.
  • 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_69d889e1c6148190ba76241e74688f8b completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e46d2eaa348190a8226eef8c0d6e31 completed April 19, 2026, 5:50 a.m.
Created at: April 10, 2026, 5:51 a.m.