Triple

T1543591
Position Surface form Disambiguated ID Type / Status
Subject Runway 4 E32925 entity
Predicate hasOrientationCategory P12663 FINISHED
Object northeast-facing runway end 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: northeast-facing runway end | Statement: [Runway 4, hasOrientationCategory, northeast-facing runway end]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasOrientationCategory
Context triple: [Runway 4, hasOrientationCategory, northeast-facing runway end]
  • A. hasOrientation chosen
    Indicates that one entity is positioned or directed in a specific spatial or conceptual alignment relative to a reference frame or another entity.
  • B. hasStripeOrientation
    Indicates the directional arrangement or alignment of stripes present on an entity.
  • C. hasFieldOrientation
    Indicates that one entity has a specified directional or spatial orientation relative to a field (such as magnetic, electric, or visual field).
  • D. supportsInternationalOrientation
    Indicates that one entity facilitates, promotes, or enables the international focus, outlook, or activities of another entity.
  • E. hasLandscapeType
    Indicates that an entity possesses or is characterized by a particular type or category of landscape.
  • 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_69a885ed29088190a3c2d5a3d100c16e completed March 4, 2026, 7:20 p.m.
NER Named-entity recognition batch_69aa95c1a2948190a2b98469afec1a7d completed March 6, 2026, 8:52 a.m.
PD Predicate disambiguation batch_69a907b2453c8190a41f6b88c8217d1e completed March 5, 2026, 4:33 a.m.
Created at: March 4, 2026, 7:26 p.m.