Triple
T33513389
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Entry/Exit System |
E858304
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | EU border management 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: EU border management system Context triple: [Entry/Exit System, instanceOf, EU border management system]
-
A.
international border system
An international border system is the coordinated set of legal frameworks, physical infrastructures, technologies, and administrative processes that regulate the movement of people, goods, and information between sovereign states.
-
B.
border control program
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.
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.
-
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.
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.
- 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_69f3497721848190978fbee5e0a526f8 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:39 a.m.