Triple

T7285732
Position Surface form Disambiguated ID Type / Status
Subject Lanzarote Airport E163861 entity
Predicate ICAOCode P419 FINISHED
Object GCRR E163861 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: GCRR | Statement: [Lanzarote Airport, ICAOCode, GCRR]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: GCRR
Context triple: [Lanzarote Airport, ICAOCode, GCRR]
  • A. GCRR chosen
    GCRR is the ICAO airport code for Lanzarote Airport, the main international gateway to the island of Lanzarote in Spain’s Canary Islands.
  • B. GCR
    GCR is the National Rail station code for Gloucester railway station in Gloucestershire, England.
  • C. CRGA
    CRGA is the acronym for the Committee of Representatives of Governments and Administrations, a body that brings together governmental and administrative representatives for coordination and decision-making.
  • D. GRR
    GRR is the IATA airport code for Gerald R. Ford International Airport, the primary commercial airport serving Grand Rapids, Michigan.
  • E. CGR
    CGR is the IATA airport code for Campo Grande International Airport in Campo Grande, Brazil.
  • 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_69c6886093b88190a254b1ce6db8bae7 completed March 27, 2026, 1:38 p.m.
NER Named-entity recognition batch_69c6eb51a8bc8190a3e1ec09ee1aeb38 completed March 27, 2026, 8:40 p.m.
NED1 Entity disambiguation (via context triple) batch_69c7e5368794819084e50bc87d8264de completed March 28, 2026, 2:27 p.m.
Created at: March 27, 2026, 2:59 p.m.