Triple

T23233735
Position Surface form Disambiguated ID Type / Status
Subject Vigo Airport E581229 entity
Predicate hasCode P9567 FINISHED
Object LEVX 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: LEVX | Statement: [Vigo Airport, hasCode, LEVX]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: LEVX
Context triple: [Vigo Airport, hasCode, LEVX]
  • A. LEVX chosen
    LEVX is the ICAO airport code for Vigo Airport, a regional international airport serving the city of Vigo in Galicia, Spain.
  • B. LEVC
    LEVC is the ICAO airport code for Valencia Airport, the main international airport serving the city of Valencia in Spain.
  • C. Evvy
    Evvy is a given name typically used as a short or affectionate form of longer names such as Evan or Evelyn.
  • D. Vy Mobility
    Vy Mobility is a Norwegian transport company within the Vy Group that operates bus and other mobility services across Norway and parts of Scandinavia.
  • E. EVZ
    EVZ is a professional Swiss ice hockey club based in Zug that competes in the National League.
  • 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_69e2460556f88190be1744a84a84173f completed April 17, 2026, 2:39 p.m.
NER Named-entity recognition batch_69f192e7bed88190b914b238c5f49860 completed April 29, 2026, 5:11 a.m.
Created at: April 17, 2026, 4:09 p.m.