Triple

T17852112
Position Surface form Disambiguated ID Type / Status
Subject Runway 08R/26L E445832 entity
Predicate runwaySystem P75082 FINISHED
Object parallel runway system at Berlin Tegel Airport 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: parallel runway system at Berlin Tegel Airport | Statement: [Runway 08R/26L, runwaySystem, parallel runway system at Berlin Tegel Airport]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: runwaySystem
Context triple: [Runway 08R/26L, runwaySystem, parallel runway system at Berlin Tegel Airport]
  • A. runway
    Indicates a relationship where a runway serves as the takeoff and landing surface used by aircraft at an airport or airfield.
  • B. runwaySurface
    Indicates the type or condition of the surface material that a runway is made of or covered with.
  • C. runwayPlan
    Indicates a planned or designated use of a runway for aircraft operations (such as takeoff, landing, or sequencing) within an airfield’s operational schedule.
  • D. runwayCharacteristic chosen
    Indicates a relationship where specific attributes or features are associated with a runway.
  • E. runwayPerformance
    Indicates the performance characteristics or behavior of an entity (such as an aircraft or vehicle) when operating on a runway, including factors like acceleration, deceleration, and required distances.
  • 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_69d8b9f26f18819089c9e43250bee6ae completed April 10, 2026, 8:50 a.m.
NER Named-entity recognition batch_69e4900113f881908859f212c6ca3d9b completed April 19, 2026, 8:19 a.m.
PD Predicate disambiguation batch_69e3d8e266888190ae976b4b7d5b886f completed April 18, 2026, 7:17 p.m.
Created at: April 10, 2026, 10:17 a.m.