Triple

T34672259
Position Surface form Disambiguated ID Type / Status
Subject 4R E890405 entity
Predicate hasComplementaryRunway P66860 FINISHED
Object 22L LITERAL 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: 22L | Statement: [4R, hasComplementaryRunway, 22L]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasComplementaryRunway
Context triple: [4R, hasComplementaryRunway, 22L]
  • A. hasOppositeRunway chosen
    Indicates that one runway is paired with another runway that has the opposite or reciprocal orientation or designation.
  • B. hasSecondaryRunway
    Indicates that an entity possesses an additional runway beyond its primary runway.
  • C. hasParallelRunway
    Indicates that one runway is parallel in orientation and alignment to another runway.
  • D. hasParallelRunwaySystemRole
    Indicates that an entity holds a specific role or function within a parallel runway system.
  • E. hasParallelRunwayIndicator
    Indicates that one runway serves as a parallel counterpart or reference indicator for another runway within an airport or airfield.
  • F. None of above.

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_69f349d9c59481908b36baa0be093aea completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_6a037c8c34f88190ace26f555827f23e completed May 12, 2026, 7:16 p.m.
PD Predicate disambiguation batch_6a0379fd7aac8190873077e63873aa72 completed May 12, 2026, 7:05 p.m.
Created at: May 1, 2026, 2:05 a.m.