Triple
T7357503
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Doncaster Sheffield Airport |
E169661
|
entity |
| Predicate | ceasedPassengerFlights |
P77039
|
FINISHED |
| Object | November 2022 |
—
|
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: November 2022 | Statement: [Doncaster Sheffield Airport, ceasedPassengerFlights, November 2022]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ceasedPassengerFlights Context triple: [Doncaster Sheffield Airport, ceasedPassengerFlights, November 2022]
-
A.
lastFlight
Indicates that one flight is the final or most recent flight taken or operated by a given entity within a specified context or sequence.
-
B.
performedFlightTo
Indicates that an entity (such as an aircraft or airline) carried out a flight whose destination was a specified location.
-
C.
usedForPassengerFlights
Indicates that something serves as a means or facility for transporting passengers on flights.
-
D.
diedOnJourneyBetween
Indicates that an entity died while traveling between two specified locations or points in a journey.
-
E.
associatedWithFlight
Indicates a relationship where an entity is linked or connected to a specific flight, such as by participation, operation, or relevance.
- 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_69c68a59f2288190877ca15c19b1e822 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f26d6d6081909c7272a9ccae0d97 |
completed | March 27, 2026, 9:11 p.m. |
| PD | Predicate disambiguation | batch_69c6f02d36108190bcb34a95e6a30bd7 |
completed | March 27, 2026, 9:01 p.m. |
| PDg | Predicate description generation | batch_69c6f26c050c8190a2d009b45d920490 |
completed | March 27, 2026, 9:11 p.m. |
Created at: March 27, 2026, 3:06 p.m.