Triple
T31056518
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Law Enforcement Directive (EU) 2016/680 |
E791412
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | EU data protection law |
C14089
|
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 data protection law Context triple: [Law Enforcement Directive (EU) 2016/680, instanceOf, EU data protection law]
-
A.
EU legal act
chosen
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.
-
B.
European Union regulation
A European Union regulation is a binding legislative act that applies directly and uniformly in all EU member states without needing national implementing measures, establishing common rules and standards across the Union.
-
C.
European Union law case
A European Union law case is a legal dispute adjudicated by the Court of Justice of the European Union or related EU judicial bodies that interprets and applies EU treaties, legislation, and legal principles among member states, institutions, or individuals.
-
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.
European Court of Justice case
A European Court of Justice case is a legal dispute brought before the Court of Justice of the European Union concerning the interpretation or validity of EU law or the actions of EU institutions and 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_69f224cb08908190ba71ad9aa87518ed |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 9 p.m.