Triple

T9738835
Position Surface form Disambiguated ID Type / Status
Subject Anderson Regional Airport E236133 entity
Predicate runway P1654 FINISHED
Object Runway 5/23 E663181 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 5/23 | Statement: [Anderson Regional Airport, runway, Runway 5/23]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Runway 5/23
Context triple: [Anderson Regional Airport, runway, Runway 5/23]
  • A. Runway 5/23 chosen
    Runway 5/23 is a primary paved runway at Molokai Airport in Hawaii, used for handling the airport’s main commercial and general aviation traffic.
  • B. Runway 5R/23L
    Runway 5R/23L is a primary paved runway at Indianapolis International Airport used for commercial and cargo aircraft operations.
  • C. Runway 5R/23L
    Runway 5R/23L is a primary paved runway at Willow Run Airport in Michigan, used mainly for cargo and general aviation operations.
  • D. Runway 5R/23L
    Runway 5R/23L is a primary paved runway at Rickenbacker International Airport in Ohio, used for handling large commercial and cargo aircraft operations.
  • E. Runway 5R/23L
    Runway 5R/23L is a primary paved runway at Piedmont Triad International Airport in North Carolina, used for commercial and general aviation operations.
  • 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_69ca84d313e88190983ee6ffd0ef60d2 completed March 30, 2026, 2:12 p.m.
NER Named-entity recognition batch_69cd9ef43fec8190987628f401a27436 completed April 1, 2026, 10:40 p.m.
NED1 Entity disambiguation (via context triple) batch_69d3170e01408190969fdd8c366f9276 completed April 6, 2026, 2:14 a.m.
Created at: March 30, 2026, 8:22 p.m.