Triple
T5429002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Visby Airport |
E121436
|
entity |
| Predicate | hasTaxiService |
P24209
|
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: [Visby Airport, hasTaxiService, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTaxiService Context triple: [Visby Airport, hasTaxiService, yes]
-
A.
hasTaxiStand
chosen
Indicates that a location or facility includes or is served by a designated taxi stand area where taxis can wait for passengers.
-
B.
hasBusServices
Indicates that one location or entity is served by bus routes or bus transportation provided by another.
-
C.
hasTugServices
Indicates that tug assistance or towing services are provided or available for a given entity or location.
-
D.
coordinatesTransportationServicesWith
Indicates that one entity organizes and manages the alignment and collaboration of transportation services with another entity or set of entities.
-
E.
hasTaxiway
Indicates that an airport or runway is connected to or served by a taxiway used for aircraft ground movement.
- 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.