Triple

T349795
Position Surface form Disambiguated ID Type / Status
Subject San Jose International Airport E7416 entity
Predicate runway P1654 FINISHED
Object Runway 12R/30L E44874 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 12R/30L | Statement: [San Jose International Airport, runway, Runway 12R/30L]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Runway 12R/30L
Context triple: [San Jose International Airport, runway, Runway 12R/30L]
  • A. Runway 12L/30R chosen
    Runway 12L/30R is one of the primary parallel runways at San Jose International Airport, used for handling a significant portion of the airport’s takeoff and landing traffic.
  • B. Runway 14L/32R
    Runway 14L/32R is one of the primary paved runways at Moffett Field in California, used for military, research, and general aviation operations.
  • C. Runway 14R/32L
    Runway 14R/32L is a primary paved runway at Moscow’s Domodedovo International Airport used for handling commercial air traffic.
  • D. Runway 14R/32L
    Runway 14R/32L is a primary paved runway at Moffett Field in California, used for military, research, and general aviation operations.
  • E. Runway 10L/28R
    Runway 10L/28R is one of the primary parallel runways at San Francisco International Airport, used extensively for both arrivals and departures.
  • 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_69a2e7e696948190bebc966535995e45 completed Feb. 28, 2026, 1:04 p.m.
NER Named-entity recognition batch_69a2eb1dc5f88190b54d084c6def7fc5 completed Feb. 28, 2026, 1:18 p.m.
NED1 Entity disambiguation (via context triple) batch_69a3e0165b6481909345301df3f2144d completed March 1, 2026, 6:43 a.m.
Created at: Feb. 28, 2026, 1:08 p.m.