Triple
T777387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London City Airport |
E16417
|
entity |
| Predicate | hasRunwayApproachType |
P19670
|
FINISHED |
| Object | steep approach |
—
|
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: steep approach | Statement: [London City Airport, hasRunwayApproachType, steep approach]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRunwayApproachType Context triple: [London City Airport, hasRunwayApproachType, steep approach]
-
A.
hasRunwayType
Indicates that an airport or airfield has a runway of a specified type or surface classification.
-
B.
runwayApproachOver
Indicates that an aircraft’s approach path to a runway passes over a particular object, area, or feature.
-
C.
hasRunwayConfiguration
Indicates a specific arrangement or setup of runways associated with an airport, airfield, or similar facility.
-
D.
hasRunwayOrientation
Indicates that a runway is aligned or oriented in a specific directional heading.
-
E.
hasInstrumentApproach
Indicates that an approach procedure to a location or runway is conducted using specified navigation instruments or instrument-based methods.
- F. None of above. chosen
Provenance (4 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_69a4936ad1fc81908f190208059ccf78 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a74da7648190adfad56717d564df |
completed | March 1, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69a4a50a443481909ae3662764ee69a4 |
completed | March 1, 2026, 8:43 p.m. |
| PDg | Predicate description generation | batch_69a4a74c81bc81909f4ac9c1677b09c2 |
completed | March 1, 2026, 8:53 p.m. |
Created at: March 1, 2026, 7:37 p.m.