Triple
T30568330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Žilina Airport |
E778049
|
entity |
| Predicate | hasPassengerServiceScope |
P175201
|
FINISHED |
| Object | regional |
—
|
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: regional | Statement: [Žilina Airport, hasPassengerServiceScope, regional]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPassengerServiceScope Context triple: [Žilina Airport, hasPassengerServiceScope, regional]
-
A.
isInPassengerService
Indicates that an entity (such as a vehicle, vessel, or aircraft) is currently being used to carry passengers as part of regular service.
-
B.
hasPassengerServicesType
chosen
Indicates the type or category of passenger services that are provided or associated with an entity.
-
C.
hasPassengerServiceLevel
Indicates the level or quality of passenger service provided in a given transportation context.
-
D.
hasPassengerServiceBrand
Indicates that a passenger transport service operates under or is associated with a specific commercial brand or service name.
-
E.
hasPassengerUsageCategory
Indicates the classification of how a passenger-related resource or service is used (e.g., its usage type or category for passengers).
- 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_69f2249f8c148190ae7eb3912cde112a |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fe5c1a502081909d4024e514309c8e |
completed | May 8, 2026, 9:56 p.m. |
| PD | Predicate disambiguation | batch_69fe5a9df21c819087153f5d0bcaa987 |
completed | May 8, 2026, 9:50 p.m. |
Created at: April 29, 2026, 8:21 p.m.