Triple
T27384098
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runway 34 |
E691317
|
entity |
| Predicate | hasReciprocalRunway |
P66860
|
FINISHED |
| Object | Runway 16 |
—
|
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: Runway 16 | Statement: [Runway 34, hasReciprocalRunway, Runway 16]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReciprocalRunway Context triple: [Runway 34, hasReciprocalRunway, Runway 16]
-
A.
hasOppositeRunway
chosen
Indicates that one runway is paired with another runway that has the opposite or reciprocal orientation or designation.
-
B.
hasParallelRunwaySystemRole
Indicates that an entity holds a specific role or function within a parallel runway system.
-
C.
hasParallelRunway
Indicates that one runway is parallel in orientation and alignment to another runway.
-
D.
hasRunwayAccessTo
Indicates that one location or facility is directly connected to another via a usable runway, allowing aircraft to move between them without leaving runway infrastructure.
-
E.
hasRunwaysAt
Indicates that a location or facility possesses one or more runways situated at that place.
- 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_69ef520386788190bc92cfcd97ebb67a |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69feb342994081909481ec8ec5d44928 |
completed | May 9, 2026, 4:08 a.m. |
| PD | Predicate disambiguation | batch_69feb046e4e48190b96649aa28529cc9 |
completed | May 9, 2026, 3:55 a.m. |
Created at: April 27, 2026, 12:23 p.m.