Triple
T33513098
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European Dactyloscopy system |
E858298
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | EU 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: EU information system Context triple: [European Dactyloscopy system, instanceOf, EU information system]
-
A.
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.
-
B.
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.
-
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.
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.
-
E.
EU legal act
An EU legal act is a binding or non-binding instrument adopted by the European Union’s institutions—such as regulations, directives, decisions, recommendations, or opinions—to create, modify, or guide the application of law within the EU legal order.
- 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.