Triple
T25822571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Visa Waiver Program |
E650440
|
entity |
| Predicate | allowsTravelFor |
P77691
|
FINISHED |
| Object | tourism |
—
|
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: tourism | Statement: [Visa Waiver Program, allowsTravelFor, tourism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowsTravelFor Context triple: [Visa Waiver Program, allowsTravelFor, tourism]
-
A.
allowsTravelAcross
Indicates that one entity enables or permits movement or passage from one side or location to another across a separating space or boundary.
-
B.
validForTravelTo
Indicates that something (such as a document, item, or condition) is acceptable or authorized for use when traveling to a specified destination.
-
C.
travelAuthorization
chosen
Indicates that permission has been granted for an entity to undertake a specific trip or journey, often under defined conditions or constraints.
-
D.
allowsReservation
Indicates that one entity permits another entity to make or hold a reservation for its use or access.
-
E.
canBeShortenedForTravelers
Indicates that something (such as a route, process, or duration) can be reduced or made shorter specifically to benefit travelers.
- 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_69e7ab367fcc8190a5ff1e7f3da046a4 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c1f94ac8190bc6fbc7916fc0d82 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 22, 2026, 7:30 a.m.