Triple
T7452671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Desks (Eurojust) |
E172043
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | judicial cooperation liaison unit |
C22248
|
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 liaison unit Context triple: [National Desks (Eurojust), instanceOf, judicial cooperation liaison unit]
-
A.
organ of the International Court of Justice
An organ of the International Court of Justice is an institutional component of the Court, such as the plenary body of judges, chambers, or administrative units, that performs specific judicial or administrative functions essential to the Court’s operation.
-
B.
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.
-
C.
international law institute
An international law institute is an organization dedicated to the study, development, teaching, and promotion of international legal norms and practices across states and global institutions.
-
D.
bilateral commission
A bilateral commission is a formal joint body established by two parties, typically states or organizations, to negotiate, coordinate, and oversee matters of mutual interest.
-
E.
Judicial conference committee
A judicial conference committee is a group of judges and related officials convened to study, discuss, and recommend policies or rules to improve the administration and operation of the court system.
- 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_69c68a66554c8190add75c65942c0317 |
completed | March 27, 2026, 1:47 p.m. |
Created at: March 27, 2026, 3:14 p.m.