Triple

T17324372
Position Surface form Disambiguated ID Type / Status
Subject GMMN E420647 entity
Predicate hasRunway P105 FINISHED
Object Runway 17L/35R — 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: Runway 17L/35R | Statement: [GMMN, hasRunway, Runway 17L/35R]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Runway 17L/35R
Context triple: [GMMN, hasRunway, Runway 17L/35R]
  • A. Runway 17L/35R
    Runway 17L/35R is one of the primary paved runways used for commercial air traffic operations at Milan Malpensa Airport in Italy.
  • B. Runway 17L/35R
    Runway 17L/35R is one of the main paved runways at Lyon–Saint-Exupéry Airport in France, used for both domestic and international air traffic operations.
  • C. Runway 17L/35R chosen
    Runway 17L/35R is a primary paved runway at Mohammed V International Airport in Casablanca, Morocco, used for handling commercial air traffic.
  • D. Runway 17L/35R
    Runway 17L/35R is a primary paved runway at North Texas Regional Airport used for general aviation and regional air traffic operations.
  • E. Runway 17L/35R
    Runway 17L/35R is one of the main paved runways at Congonhas–São Paulo Airport, used for intensive domestic air traffic operations in São Paulo, Brazil.
  • 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_69d889d3adc881909319f1edb8d2a956 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e439d18e3081908ca15baa743abcd8 completed April 19, 2026, 2:11 a.m.
Created at: April 10, 2026, 5:43 a.m.