Triple
T18430201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kalibo International Airport |
E450246
|
entity |
| Predicate | servesInternationalTourists |
P17187
|
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: [Kalibo International Airport, servesInternationalTourists, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesInternationalTourists Context triple: [Kalibo International Airport, servesInternationalTourists, yes]
-
A.
servesTravelersTo
Indicates a relationship where one entity provides services, assistance, or accommodations specifically directed toward travelers heading to a particular destination.
-
B.
touristAccess
chosen
Indicates that a place or resource is available for use or visitation by tourists.
-
C.
connectsToTouristRegion
Indicates that one entity has a direct linkage or association to a tourist region, such as through location, access, or service provision.
-
D.
hasTouristVisits
Indicates that one entity experiences or records visits from tourists to another entity.
-
E.
tourismFrom
Indicates that tourists or visitor activity originates from one place and is directed toward another location.
- 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_69d8d381d6388190a9e94e9c658174e4 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e51b16b9c881908245c888a4b785bf |
completed | April 19, 2026, 6:12 p.m. |
| PD | Predicate disambiguation | batch_69e469c943a4819094c8fdc5971ad3a7 |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:26 a.m.