Triple

T5957351
Position Surface form Disambiguated ID Type / Status
Subject Aeroporto di Roma–Fiumicino E132549 entity
Predicate ICAOcode P419 FINISHED
Object LIRF E124981 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: LIRF | Statement: [Aeroporto di Roma–Fiumicino, ICAOcode, LIRF]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: LIRF
Context triple: [Aeroporto di Roma–Fiumicino, ICAOcode, LIRF]
  • A. LIRF chosen
    LIRF is the ICAO airport code for Leonardo da Vinci–Fiumicino Airport, the main international airport serving Rome, Italy.
  • B. LIRJ
    LIRJ is the ICAO airport code for Marina di Campo Airport, a small regional airport serving Elba Island in Italy.
  • C. LIF
    LIF is the vehicle registration code for the town and district of Lichtenfels in the German state of Bavaria.
  • D. LIR Portal
    LIR Portal is an online platform provided by the RIPE NCC that allows Local Internet Registries to manage their IP address and ASN resources and related administrative tasks.
  • E. LFRS
    LFRS is the ICAO airport code for Nantes Atlantique Airport, a major international airport serving the city of Nantes in western France.
  • 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_69c0086b05cc8190a8f36a96927a525c completed March 22, 2026, 3:19 p.m.
NER Named-entity recognition batch_69c039c34ca881909a219eddf99348ab completed March 22, 2026, 6:49 p.m.
NED1 Entity disambiguation (via context triple) batch_69c0e3dd99888190ac3eeef692a7d879 completed March 23, 2026, 6:55 a.m.
Created at: March 22, 2026, 4:02 p.m.