Triple
T18214013
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bern Airport |
E436104
|
entity |
| Predicate | hasCharterFlights |
P81835
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Bern Airport, hasCharterFlights, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCharterFlights Context triple: [Bern Airport, hasCharterFlights, yes]
-
A.
supportsCharterFlights
Indicates that one entity provides the capability or service of operating or accommodating charter flights for another entity.
-
B.
operatedCharterFlights
Indicates that an entity conducted or managed charter flight services for another entity or purpose.
-
C.
hasDomesticFlights
Indicates that an airline or airport operates flights within the same country, connecting domestic destinations.
-
D.
hasCharterServices
chosen
Indicates that an entity provides or is associated with charter-based transportation or service offerings for another entity.
-
E.
hasTypeOfFlights
Indicates that an entity offers, includes, or is associated with specific categories or kinds of flights.
- 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_69d8b90dba6481908e119eb9aa4ca0cb |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4e475953c81909f792793ded2057e |
completed | April 19, 2026, 2:19 p.m. |
| PD | Predicate disambiguation | batch_69e4332155d88190b106d0dceb4554af |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:32 a.m.