Triple
T28388374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SIS II |
E719084
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Schengen Information System |
C27916
|
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: [SIS II, 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.
European Union information system
chosen
A European Union information system is an integrated digital platform that collects, processes, stores, and exchanges data across EU institutions and member states to support policymaking, administration, and regulatory compliance.
-
C.
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.
-
D.
EU database
An EU database is a structured, centralized repository managed by or for European Union institutions to store, organize, and provide controlled access to data relevant to EU policies, regulations, operations, or member states.
-
E.
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.
- 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_69eff6ef211081909d31d9be5f5567e6 |
completed | April 27, 2026, 11:53 p.m. |
Created at: April 28, 2026, 1:11 a.m.