Triple
T7816479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phu Quoc International Airport |
E181017
|
entity |
| Predicate | supportsVisaOnArrival |
P79167
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Phu Quoc International Airport, supportsVisaOnArrival, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsVisaOnArrival Context triple: [Phu Quoc International Airport, supportsVisaOnArrival, true]
-
A.
shareVisaPolicy
Indicates that two entities apply the same or highly similar visa requirements and entry rules to travelers.
-
B.
visaRequirement
Indicates whether one party must obtain a visa in order to enter, stay in, or transit through the territory of another party.
-
C.
hasConsularEntranceOn
Indicates that a consular facility or office has an entrance located on a specified street, side, or access point.
-
D.
supportsNonSchengenFlights
Indicates that the subject facility or service is capable of handling or accommodating flights that operate outside the Schengen Area.
-
E.
supportsSchengenFlights
Indicates that an entity enables or accommodates flights operating within the Schengen Area.
- F. None of above. chosen
Provenance (4 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_69ca828153f48190bdb27ac46f8e0745 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69caf96ea6d881908eff5f750e0f6700 |
completed | March 30, 2026, 10:30 p.m. |
| PD | Predicate disambiguation | batch_69cae91687788190af9cb7aaa996d291 |
completed | March 30, 2026, 9:20 p.m. |
| PDg | Predicate description generation | batch_69caf7855a3c81908b9318f7186fc0c0 |
completed | March 30, 2026, 10:21 p.m. |
Created at: March 30, 2026, 4:39 p.m.