Triple
T3012105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terminal 2 |
E82245
|
entity |
| Predicate | hasRunwayAccessViaAirport |
P18604
|
FINISHED |
| Object | Runways of London Heathrow 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: Runways of London Heathrow Airport | Statement: [Terminal 2, hasRunwayAccessViaAirport, Runways of London Heathrow Airport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRunwayAccessViaAirport Context triple: [Terminal 2, hasRunwayAccessViaAirport, Runways of London Heathrow Airport]
-
A.
hasRunwayAccessVia
chosen
Indicates that an entity has access to a runway by means of a specified connecting route, facility, or intermediary.
-
B.
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.
-
C.
hasRunwayUse
Indicates that a particular runway is authorized or designated for use by a specific aircraft, operation, or purpose.
-
D.
airportAccessMode
Indicates the typical mode or method of transportation used to access or reach an airport.
-
E.
hasRunwayType
Indicates that an airport or airfield has a runway of a specified type or surface classification.
- 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_69ad8b1eb53481908c39bbcd1ec104b2 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9a66c334819082d1d320c48eca1b |
completed | March 8, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69ad961a97188190809dc73430a8eda8 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3 p.m.