Triple

T14469436
Position Surface form Disambiguated ID Type / Status
Subject Pasila, Helsinki E358797 entity
Predicate hasPublicTransportOperator P14525 FINISHED
Object HSL E410284 NE FINISHED

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: HSL | Statement: [Pasila, Helsinki, hasPublicTransportOperator, HSL]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: HSL
Context triple: [Pasila, Helsinki, hasPublicTransportOperator, HSL]
  • A. HSL chosen
    HSL is the public transport authority responsible for planning and organizing bus, tram, metro, commuter rail, and ferry services in the Helsinki metropolitan area of Finland.
  • B. HSL
    HSL is the three-letter National Rail station code for Haslemere railway station in Surrey, England.
  • C. HSL
    HSL is a record label known for releasing music by the New Zealand rock band The Datsuns.
  • D. HSB
    HSB is a specialty insurance and engineering services company best known for its expertise in equipment breakdown coverage and risk management solutions.
  • E. HSB
    HSB is a historic narrow-gauge railway network in Germany’s Harz mountains, popular for its steam-powered tourist trains and scenic routes.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 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_69d827966698819082e140837737501d completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de91f969788190a5114f92d7159aae completed April 14, 2026, 7:14 p.m.
NED1 Entity disambiguation (via context triple) batch_69fd649beec88190861abb52c5a2733e completed May 8, 2026, 4:20 a.m.
Created at: April 10, 2026, 1:20 a.m.