Triple
T10341751
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prüm Decisions |
E243142
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | judicial cooperation measure |
C2063
|
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: judicial cooperation measure Context triple: [Prüm Decisions, instanceOf, judicial cooperation measure]
-
A.
judicial cooperation liaison unit
A judicial cooperation liaison unit is a specialized body that facilitates communication, coordination, and mutual legal assistance between national and international judicial authorities to support cross-border investigations and prosecutions.
-
B.
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.
-
C.
international cooperation mechanism
chosen
An international cooperation mechanism is a structured framework, agreement, or institution through which multiple countries coordinate policies, share resources, and jointly address cross-border issues or common goals.
-
D.
judicial investigation
A judicial investigation is a formal, legally authorized inquiry conducted by judicial authorities to gather, examine, and evaluate evidence in order to determine whether laws have been violated and if legal proceedings should follow.
-
E.
judicial network
A judicial network is a structured system of interconnected courts, judges, and legal institutions that interact through case decisions, precedents, and administrative relationships to shape and apply the law.
- 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_69d381af787481908bc401325c760a88 |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 11:55 a.m.