Triple

T12034955
Position Surface form Disambiguated ID Type / Status
Subject Runway 09L/27R E286512 entity
Predicate hasLeftRightDesignator P54806 FINISHED
Object L for 09 direction 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: L for 09 direction | Statement: [Runway 09L/27R, hasLeftRightDesignator, L for 09 direction]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasLeftRightDesignator
Context triple: [Runway 09L/27R, hasLeftRightDesignator, L for 09 direction]
  • A. hasPortionDesignatedAs
    Indicates that one entity has a specific part or segment that is explicitly identified or designated as another entity.
  • B. hasRunwayDesignationSide chosen
    Indicates that a runway designation is associated with a specific side or direction of the runway (e.g., left, right, or center).
  • C. isDesignatedRight
    Indicates that something has been formally assigned or recognized as the correct or official right in a given context.
  • D. hasDesignOption
    Indicates that an entity is associated with or offers a particular design alternative or configurable design choice.
  • E. hasLateralityPattern
    Indicates that something possesses a specific sidedness or lateral arrangement (e.g., left, right, bilateral) as a characteristic pattern.
  • 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_69d6ab4669e48190b59246358b0383ab completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d9100b4ca8819084845ca4c13e34ce completed April 10, 2026, 2:58 p.m.
PD Predicate disambiguation batch_69d902b6ebbc8190b13c44a61c6f81b9 completed April 10, 2026, 2:01 p.m.
Created at: April 8, 2026, 9:47 p.m.