Triple

T15820679
Position Surface form Disambiguated ID Type / Status
Subject Harrisburg International Airport E383597 entity
Predicate hasRunway P105 FINISHED
Object Runway 13/31 E690422 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: Runway 13/31 | Statement: [Harrisburg International Airport, hasRunway, Runway 13/31]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Runway 13/31
Context triple: [Harrisburg International Airport, hasRunway, Runway 13/31]
  • A. Runway 13/31
    Runway 13/31 is a primary paved runway at Trapani–Birgi Airport in Sicily, Italy, used for both civilian and military aircraft operations.
  • B. Runway 13/31
    Runway 13/31 is a primary paved runway at Islay Airport in Scotland, used for regional passenger and general aviation flights.
  • C. Runway 13/31
    Runway 13/31 is a principal paved runway used for aircraft takeoffs and landings at Pinto Martins – Fortaleza International Airport in Fortaleza, Brazil.
  • D. Runway 13/31 chosen
    Runway 13/31 is a primary paved runway at Rochester International Airport used for handling a range of commercial and general aviation aircraft operations.
  • E. Runway 13/31
    Runway 13/31 is a primary paved runway at Lancaster Regional Airport used for general aviation takeoffs and landings.
  • 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_69d86da2858c819090cc8481e7207b6e completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e0c4a7ba4881908a2747bf063d79f1 completed April 16, 2026, 11:14 a.m.
NED1 Entity disambiguation (via context triple) batch_69ffbe69332c81909aa57e64de163cbe completed May 9, 2026, 11:08 p.m.
Created at: April 10, 2026, 4:49 a.m.