Triple
T10341845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Visa Information System |
E243144
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Schengen information system |
C6282
|
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: Schengen information system Context triple: [Visa Information System, instanceOf, Schengen information system]
-
A.
Europol system
The Europol system is an integrated information and coordination platform that supports European law enforcement agencies in sharing intelligence, analyzing criminal data, and coordinating cross-border investigations.
-
B.
border control program
chosen
A border control program is a coordinated set of policies, procedures, and technologies designed to regulate and monitor the movement of people and goods across a country's borders to ensure security, compliance, and lawful entry.
-
C.
component of Eurojust
A component of Eurojust is an organizational unit or structural element within the Eurojust agency that contributes to its mission of coordinating judicial cooperation in criminal matters among EU member states.
-
D.
border control agency
A border control agency is a governmental organization responsible for regulating and monitoring the movement of people and goods across a country's borders to ensure security, compliance with laws, and protection of national interests.
-
E.
organ of Europol
An organ of Europol is an official institutional body within the European Union Agency for Law Enforcement Cooperation that performs specific governance, oversight, advisory, or operational functions in support of Europol’s mandate.
- F. None of above.
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_69d381af787481908bc401325c760a88 |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 11:55 a.m.