Triple

T19965266
Position Surface form Disambiguated ID Type / Status
Subject Genoa Cristoforo Colombo Airport E479914 entity
Predicate hasICAOCode P419 FINISHED
Object LIMJ 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: LIMJ | Statement: [Genoa Cristoforo Colombo Airport, hasICAOCode, LIMJ]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: LIMJ
Context triple: [Genoa Cristoforo Colombo Airport, hasICAOCode, LIMJ]
  • A. LIMJ chosen
    LIMJ is the ICAO airport code for Genoa Cristoforo Colombo Airport, the main international airport serving the city of Genoa in Italy.
  • B. LIM
    LIM is the IATA airport code for Jorge Chávez International Airport, the main international gateway serving Lima, Peru.
  • C. LIMC
    LIMC is the ICAO airport code for Milan Malpensa Airport, a major international airport serving the Milan metropolitan area in Italy.
  • D. LIMW
    LIMW is the ICAO airport code for Aosta Valley Airport, a regional airport serving Italy’s Aosta Valley in the Alps.
  • E. LIMF
    LIMF is the ICAO airport code for Turin Airport, an international airport serving the city of Turin in northern Italy.
  • 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_69d8e523c19881909f9197037200dde6 completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e65bc4f47c8190a721f5e488150d81 completed April 20, 2026, 5 p.m.
Created at: April 10, 2026, 1:54 p.m.