Triple
T10929642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wail al-Shehri |
E258165
|
entity |
| Predicate | visaType |
P93859
|
FINISHED |
| Object | tourist visa |
—
|
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: tourist visa | Statement: [Wail al-Shehri, visaType, tourist visa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: visaType Context triple: [Wail al-Shehri, visaType, tourist visa]
-
A.
visaRequirement
Indicates whether one party must obtain a visa in order to enter, stay in, or transit through the territory of another party.
-
B.
shareVisaPolicy
Indicates that two entities apply the same or highly similar visa requirements and entry rules to travelers.
-
C.
usedVisaType
chosen
Indicates that a particular type of visa was utilized in the context of an action, transaction, or event involving the related entities.
-
D.
supportsVisaOnArrival
Indicates that a country or authority allows eligible travelers to obtain a visa upon arrival rather than requiring it in advance.
-
E.
travelDocumentRequirement
Indicates that a specific type of travel document is required for an entity (e.g., a person or trip) to undertake or complete a particular journey or border crossing.
- 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_69d6aa8769b4819082bfe5e61b9017f0 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7709eb0ec819093f7d3f99097bbe4 |
completed | April 9, 2026, 9:25 a.m. |
| PD | Predicate disambiguation | batch_69d72e799f808190b6ab64fc7586a303 |
completed | April 9, 2026, 4:43 a.m. |
Created at: April 8, 2026, 9:22 p.m.