Triple

T21332120
Position Surface form Disambiguated ID Type / Status
Subject Runway 15/33 E525930 entity
Predicate icaoAirportCode P419 FINISHED
Object EFHK 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: EFHK | Statement: [Runway 15/33, icaoAirportCode, EFHK]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: EFHK
Context triple: [Runway 15/33, icaoAirportCode, EFHK]
  • A. EFHK chosen
    EFHK is the ICAO airport code for Helsinki Airport, the main international gateway to Finland located near the capital city.
  • B. NHF
    NHF is the abbreviation for the National Historic Fleet, a register of historically significant vessels in the United Kingdom.
  • C. NHF
    NHF is the Norwegian Handball Federation, the national governing body responsible for organizing and overseeing handball in Norway, including the Norway men's national handball team.
  • D. IHF
    IHF is the commonly used abbreviation for the International Handball Federation, the global governing body for the sport of handball.
  • E. ECAHA
    ECAHA is the acronym for the Eastern Canada Amateur Hockey Association, a historical ice hockey league that operated in eastern Canada.
  • 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_69e0b51b90788190a4dd823d962626da completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e7ab54706081909445f9cd91a43788 completed April 21, 2026, 4:52 p.m.
Created at: April 16, 2026, 4:42 p.m.