Triple
T36296304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wail Mohammed al-Shehri |
E893376
|
entity |
| Predicate | entryMethodToUnitedStates |
P92645
|
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 Mohammed al-Shehri, entryMethodToUnitedStates, tourist visa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: entryMethodToUnitedStates Context triple: [Wail Mohammed al-Shehri, entryMethodToUnitedStates, tourist visa]
-
A.
entryToUnitedStatesDate
Indicates the date on which an entity entered the United States.
-
B.
borderWithUnitedStatesVia
Indicates that one entity shares a border with the United States specifically through or along the second entity (such as a body of water, territory, or region).
-
C.
borderAgencyUnitedStates
Indicates that the agency operates as or is part of the border control or border security authority of the United States.
-
D.
enteredCountryVia
chosen
Indicates that an entity came into a country using a specific entry point, route, or method.
-
E.
visaRequirement
Indicates whether one party must obtain a visa in order to enter, stay in, or transit through the territory of another party.
- 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_69f76e4a61f0819084a2b68dbbb4efc6 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bcccd7988190aa5c931ff347d33c |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:09 p.m.