Triple

T16344653
Position Surface form Disambiguated ID Type / Status
Subject Heathrow Runway 09L/27R E396898 entity
Predicate isConfiguredAs P13644 FINISHED
Object left-hand runway for easterly operations 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: left-hand runway for easterly operations | Statement: [Heathrow Runway 09L/27R, isConfiguredAs, left-hand runway for easterly operations]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isConfiguredAs
Context triple: [Heathrow Runway 09L/27R, isConfiguredAs, left-hand runway for easterly operations]
  • A. hasConfiguration chosen
    Indicates that an entity is associated with or defined by a particular configuration or setup.
  • B. partlyConfiguredAs
    Indicates that one entity is only partially set up, arranged, or defined to function as another entity or in another role.
  • C. isZeroConfiguration
    Indicates that something requires no manual setup or configuration to function correctly.
  • D. oftenConfiguredAs
    Indicates that one entity is frequently set up, arranged, or used in the form or role of another entity.
  • E. appliesToConfiguration
    Indicates that something (such as a rule, setting, or operation) is relevant to, affects, or is intended for a particular configuration.
  • 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_69d87f26864c819088365ca381a003c2 completed April 10, 2026, 4:40 a.m.
NER Named-entity recognition batch_69e2da0da1808190b6477613a07c7a88 completed April 18, 2026, 1:10 a.m.
PD Predicate disambiguation batch_69e226eba9b48190af6e80d3d1c2aed3 completed April 17, 2026, 12:26 p.m.
Created at: April 10, 2026, 5:07 a.m.