Triple
T10341702
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eurodac system |
E243141
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | European Union 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: European Union information system Context triple: [Eurodac system, instanceOf, European Union 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 convention
A European Union convention is a formal international agreement between EU member states, or between the EU and other parties, that establishes common rules, standards, or cooperation frameworks in specific policy areas.
-
C.
United Nations information system
A United Nations information system is an integrated framework of technologies, databases, and processes used across UN entities to collect, manage, analyze, and disseminate data and knowledge in support of the organization’s mandates and decision-making.
-
D.
European organisation
A European organisation is an entity based in or primarily serving Europe that coordinates activities, policies, or services across multiple European countries or within a specific European nation.
-
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. 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_69d381af787481908bc401325c760a88 |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 11:55 a.m.