Triple

T27384105
Position Surface form Disambiguated ID Type / Status
Subject Runway 34 E691317 entity
Predicate isDesignatedAccordingTo P162652 FINISHED
Object FAA runway numbering convention 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: FAA runway numbering convention | Statement: [Runway 34, isDesignatedAccordingTo, FAA runway numbering convention]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isDesignatedAccordingTo
Context triple: [Runway 34, isDesignatedAccordingTo, FAA runway numbering convention]
  • A. isDesignatedRight
    Indicates that something has been formally assigned or recognized as the correct or official right in a given context.
  • B. canBeDesignatedBy
    Indicates that one entity is capable of being assigned, labeled, or identified by another entity as its designation.
  • C. wasDesignatedBy
    Indicates that an entity received an official status, role, or label as the result of a formal act or decision performed by another agent or authority.
  • D. isDesignedAs
    Indicates that something has been intentionally created or configured to serve as or function in the role of something else.
  • E. hasDesignationCriteria
    Indicates that a designation, status, or category is assigned based on specific criteria or conditions.
  • F. None of above. chosen

Provenance (4 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_69ef520386788190bc92cfcd97ebb67a completed April 27, 2026, 12:09 p.m.
NER Named-entity recognition batch_69f62d89b89c8190afb372a8172111e7 completed May 2, 2026, 4:59 p.m.
PD Predicate disambiguation batch_69f62c1762f881908c25e8f70ecd5041 completed May 2, 2026, 4:53 p.m.
PDg Predicate description generation batch_69f62cd1912c8190ab3f3288442115a4 completed May 2, 2026, 4:56 p.m.
Created at: April 27, 2026, 12:23 p.m.