Triple
T26463634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fiches Belges |
E665700
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | European Judicial Network tool |
C14105
|
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 Judicial Network tool Context triple: [Fiches Belges, instanceOf, European Judicial Network tool]
-
A.
judicial network
chosen
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.
-
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.
European Union information system
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.
-
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_69ee883e812c8190a9b5a9cdb87fee5e |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 27, 2026, 12:14 a.m.