Triple
T33513242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VIS |
E858301
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | visa information system |
C59907
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: visa information system Context triple: [VIS, instanceOf, visa information system]
-
A.
student and exchange visitor tracking system
A student and exchange visitor tracking system is a centralized platform that records, monitors, and manages the status, activities, and compliance of international students and exchange visitors throughout their academic or program lifecycle.
-
B.
passport union
A passport union is an agreement between two or more jurisdictions that allows citizens to travel, reside, and often work across member states using a shared or mutually recognized passport system with minimal border controls.
-
C.
passport authority
An organization or government agency responsible for issuing, renewing, and regulating passports and related travel documents for citizens.
-
D.
United States nonimmigrant visa
A United States nonimmigrant visa is a temporary authorization granted to foreign nationals that permits them to travel to a U.S. port of entry and request admission for a specific, limited purpose such as tourism, study, or work.
-
E.
travel document standard
A travel document standard is a formalized set of rules and specifications that define the structure, security features, data formats, and interoperability requirements for official documents used to identify and authorize individuals for international travel.
- F. None of above. chosen
Provenance (1 batch)
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_69f3497721848190978fbee5e0a526f8 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:39 a.m.