Triple

T18020635
Position Surface form Disambiguated ID Type / Status
Subject Inner and Outer Hebrides air network E431107 entity
Predicate hasLandingType P118651 FINISHED
Object conventional runway landings 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: conventional runway landings | Statement: [Inner and Outer Hebrides air network, hasLandingType, conventional runway landings]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasLandingType
Context triple: [Inner and Outer Hebrides air network, hasLandingType, conventional runway landings]
  • A. hasLandingConditions
    Indicates the specific conditions or requirements that must be met for a landing to occur or be permitted.
  • B. hasLandingCharacteristics chosen
    Indicates that an entity possesses specific attributes or features related to how it lands or is capable of landing.
  • C. hasIslandLanding
    Indicates that an entity includes or provides a designated landing area or facility located on an island.
  • D. hasLandingSystem
    Indicates that an entity is equipped with or utilizes a particular landing system for performing landings.
  • E. hasLandComponent
    Indicates that something includes, consists of, or is associated with a land-based part or portion as one of its components.
  • 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_69d8b904530081908bf341d842464856 completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e4b9c1c5f88190a059ce4f86f7ed36 completed April 19, 2026, 11:17 a.m.
PD Predicate disambiguation batch_69e3f904b8048190add43883cd7cb191 completed April 18, 2026, 9:35 p.m.
Created at: April 10, 2026, 10:24 a.m.