Triple
T5353200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gothenburg City Airport |
E102625
|
entity |
| Predicate | reasonForCommercialClosure |
P8451
|
FINISHED |
| Object | runway safety concerns |
—
|
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: runway safety concerns | Statement: [Gothenburg City Airport, reasonForCommercialClosure, runway safety concerns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForCommercialClosure Context triple: [Gothenburg City Airport, reasonForCommercialClosure, runway safety concerns]
-
A.
closureReason
chosen
Indicates the reason or cause for which an entity, process, or case has been closed or terminated.
-
B.
announcedPermanentClosure
Indicates that an entity has formally stated that it will cease operations or availability indefinitely and not reopen.
-
C.
reasonForDisbandment
Indicates the cause or circumstance that led to a group, organization, or entity being dissolved or disbanded.
-
D.
closedVenue
Indicates that a venue is not open or available for use during a given time or event.
-
E.
reasonForDemolition
Indicates the cause, justification, or circumstance that led to a structure or object being demolished.
- 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_69bd43d8f7248190b64c140734b5c9a8 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd861327288190b3f2720ce81e0de6 |
completed | March 20, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69bd845c6f108190832a8d14b356368a |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:01 p.m.