Triple
T6588480
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luton Airport Parkway |
E159287
|
entity |
| Predicate | airportLinkReplaced |
P71655
|
FINISHED |
| Object | shuttle bus service |
—
|
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: shuttle bus service | Statement: [Luton Airport Parkway, airportLinkReplaced, shuttle bus service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airportLinkReplaced Context triple: [Luton Airport Parkway, airportLinkReplaced, shuttle bus service]
-
A.
replacedAsMainAirportFor
Indicates that one airport has taken over the role of being the primary or main airport serving a particular area from another airport.
-
B.
associatedAirport
Indicates a relationship where an entity is linked or connected to a specific airport, typically as its relevant or corresponding airport.
-
C.
airportAlsoKnownAs
Indicates that an airport is referred to by an alternative name or alias in addition to its primary name.
-
D.
airportUse
Indicates that an airport is used or utilized by a particular entity, such as an airline, organization, or service.
-
E.
airportStation
Indicates a location functions as an airport facility where air transport operations occur.
- 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_69c688366ce8819083f8883983c0df92 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6c07cdf048190945ca5810fb1de88 |
completed | March 27, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69c6acfb462481909cb7aff5af4bca9d |
completed | March 27, 2026, 4:14 p.m. |
| PDg | Predicate description generation | batch_69c6c07bb434819096ec3e3b966042a5 |
completed | March 27, 2026, 5:38 p.m. |
Created at: March 27, 2026, 1:55 p.m.