Triple
T21184520
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runway 04R/22L |
E522043
|
entity |
| Predicate | parallelRunwaySystem |
P11810
|
FINISHED |
| Object | 04/22 runway pair at Nice Côte d’Azur 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: 04/22 runway pair at Nice Côte d’Azur Airport | Statement: [Runway 04R/22L, parallelRunwaySystem, 04/22 runway pair at Nice Côte d’Azur Airport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parallelRunwaySystem Context triple: [Runway 04R/22L, parallelRunwaySystem, 04/22 runway pair at Nice Côte d’Azur Airport]
-
A.
hasParallelRunway
chosen
Indicates that one runway is parallel in orientation and alignment to another runway.
-
B.
hasParallelRunwayIndicator
Indicates that one runway serves as a parallel counterpart or reference indicator for another runway within an airport or airfield.
-
C.
runway
Indicates a relationship where a runway serves as the takeoff and landing surface used by aircraft at an airport or airfield.
-
D.
runwayConstructed
Indicates that a runway has been built or established at a particular location.
-
E.
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.
- 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_69e0b50ef1d48190b063aa342667df22 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e730205ce88190b0bb33003295d6e7 |
completed | April 21, 2026, 8:06 a.m. |
| PD | Predicate disambiguation | batch_69e5f6027c248190a170a36612bd337e |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:06 p.m.