Triple
T7452761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European Arrest Warrant |
E172045
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | judicial cooperation instrument |
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 instrument Context triple: [European Arrest Warrant, instanceOf, judicial cooperation instrument]
-
A.
trade in services instrument
A trade in services instrument is a financial or contractual mechanism that facilitates, records, or manages cross-border transactions involving the provision of services rather than physical goods.
-
B.
international agreement implementation area
The international agreement implementation area is a defined domain—such as a sector, region, or policy field—within which the provisions of an international agreement are applied, monitored, and enforced.
-
C.
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.
-
D.
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.
-
E.
intergovernmental working group framework
An intergovernmental working group framework is a structured, collaborative arrangement through which multiple governments coordinate, negotiate, and develop joint policies, standards, or actions on shared issues.
- 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_69c68a66554c8190add75c65942c0317 |
completed | March 27, 2026, 1:47 p.m. |
Created at: March 27, 2026, 3:14 p.m.