Triple
T5429024
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Visby Airport |
E121436
|
entity |
| Predicate | supportsAirlinesType |
P9478
|
FINISHED |
| Object | scheduled airlines |
—
|
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: scheduled airlines | Statement: [Visby Airport, supportsAirlinesType, scheduled airlines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsAirlinesType Context triple: [Visby Airport, supportsAirlinesType, scheduled airlines]
-
A.
servesAirlineType
chosen
Indicates that a service provider (such as an airport, terminal, or facility) accommodates or operates flights for a specified type or category of airline.
-
B.
hasAirlines
Indicates that one entity (such as an airport, city, or country) is served by or associated with one or more airline operators.
-
C.
airlineType
Indicates the classification or category of an airline based on its operational or service characteristics.
-
D.
servesAirline
Indicates that a transportation facility or location provides service for, or is regularly used by, a specified airline.
-
E.
ownsAirline
Indicates that one entity has legal ownership or controlling interest in an airline company.
- 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_69bd463c65f0819082ee6483ab4b466a |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd8911a7348190ad9378a248190f07 |
completed | March 20, 2026, 5:51 p.m. |
| PD | Predicate disambiguation | batch_69bd846b8bdc81909dcdc2a3084226f2 |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:06 p.m.