Triple

T22514940
Position Surface form Disambiguated ID Type / Status
Subject Widerøe E556616 entity
Predicate radioCallsign P1565 FINISHED
Object WIDEROE 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: WIDEROE | Statement: [Widerøe, radioCallsign, WIDEROE]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: WIDEROE
Context triple: [Widerøe, radioCallsign, WIDEROE]
  • A. WIDEROE chosen
    WIDEROE is the radio callsign used by Widerøe, a Norwegian regional airline operating domestic and short-haul international flights.
  • B. WAGON AIR
    WAGON AIR is the radio callsign used by the Indonesian low-cost airline AirAsia Indonesia for air traffic communications.
  • C. Valdresflye
    Valdresflye is a high mountain plateau and scenic driving route in central Norway, renowned for its expansive views, hiking opportunities, and access to the Jotunheimen region.
  • D. Equair
    Equair is an Ecuadorian airline that operated domestic passenger flights, notably serving routes from Guayaquil and Quito.
  • E. VUELING
    VUELING is a Spanish low-cost airline based in Barcelona that operates extensive domestic and European routes.
  • 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_69e11e555edc81909ca803587dafd747 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f15e2c3098819098a553133cc9515b completed April 29, 2026, 1:26 a.m.
Created at: April 16, 2026, 8:50 p.m.