Triple
T34672260
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 4R |
E890405
|
entity |
| Predicate | hasReciprocalRunwayNumber |
—
|
GENERATED |
| Object | 22 |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReciprocalRunwayNumber Context triple: [4R, hasReciprocalRunwayNumber, 22]
-
A.
hasOppositeRunway
chosen
Indicates that one runway is paired with another runway that has the opposite or reciprocal orientation or designation.
-
B.
hasParallelRunwayIndicator
Indicates that one runway serves as a parallel counterpart or reference indicator for another runway within an airport or airfield.
-
C.
hasParallelRunwaySystemRole
Indicates that an entity holds a specific role or function within a parallel runway system.
-
D.
hasRunwayNumber
Indicates that an airport or airfield runway is assigned a specific identifying number.
-
E.
hasRunwayNumberRange
Indicates that an entity (such as an airport or airfield) has runways whose identification numbers fall within a specified numeric range.
- F. None of above.
Provenance (1 batch)
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_69f349d9c59481908b36baa0be093aea |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 2:05 a.m.