Triple
T14930224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berlin Schönefeld Airport |
E372240
|
entity |
| Predicate | closedForPassengerFlights |
P10433
|
FINISHED |
| Object | 2020 |
—
|
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: 2020 | Statement: [Berlin Schönefeld Airport, closedForPassengerFlights, 2020]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: closedForPassengerFlights Context triple: [Berlin Schönefeld Airport, closedForPassengerFlights, 2020]
-
A.
closedForPassengers
chosen
Indicates that a transportation facility or vehicle is not available for use by passengers.
-
B.
closedForFlightOperations
Indicates that a location, facility, or area is temporarily unavailable or prohibited for conducting flight operations.
-
C.
openedToPassengerTraffic
Indicates that a transportation facility or route began operating and accepting passengers for regular use.
-
D.
usedForPassengerFlights
Indicates that something serves as a means or facility for transporting passengers on flights.
-
E.
supportsNonSchengenFlights
Indicates that the subject facility or service is capable of handling or accommodating flights that operate outside the Schengen Area.
- 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_69d85cc9da0c81908d583ca3f63a3908 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded64550dc8190ba44120df00ba498 |
completed | April 15, 2026, 12:05 a.m. |
| PD | Predicate disambiguation | batch_69de9a52ba988190a26e268b4ea083ea |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:36 a.m.