Triple
T30622080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vitoria Airport |
E779474
|
entity |
| Predicate | passengerServicesLevel |
P175201
|
FINISHED |
| Object | limited |
—
|
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: limited | Statement: [Vitoria Airport, passengerServicesLevel, limited]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: passengerServicesLevel Context triple: [Vitoria Airport, passengerServicesLevel, limited]
-
A.
hasPassengerServicesTo
Indicates that a transportation provider operates passenger services connecting one location or entity to another.
-
B.
hasPassengerServicesType
chosen
Indicates the type or category of passenger services that are provided or associated with an entity.
-
C.
majorPassengerService
Indicates that a transportation facility or route provides primary or significant passenger service as one of its main functions.
-
D.
hasPassengerServiceBrand
Indicates that a passenger transport service operates under or is associated with a specific commercial brand or service name.
-
E.
passengerConvenience
Indicates how convenient or comfortable a service, vehicle, or facility is for passengers to use.
- 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_69f224a3307081909a6dca8ca75dbf48 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6e6029a10819098ff21f58079e70e |
completed | May 3, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d5e8188190b1e1c2e5d1b77031 |
completed | May 3, 2026, 5:57 a.m. |
Created at: April 29, 2026, 8:27 p.m.