Triple
T27013643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eurojust cooperation network |
E680464
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | European Union network |
C14427
|
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 Union network Context triple: [Eurojust cooperation network, instanceOf, European Union network]
-
A.
European university network
A European university network is a collaborative association of higher education institutions across Europe that coordinate academic programs, research initiatives, and mobility opportunities to enhance education and innovation.
-
B.
European organisation
chosen
A European organisation is an entity based in or primarily serving Europe that coordinates activities, policies, or services across multiple European countries or within a specific European nation.
-
C.
eurodistrict
A eurodistrict is a cross-border administrative and cooperation entity formed by neighboring local authorities from different European countries to coordinate services, planning, and development in a shared transnational region.
-
D.
European Union convention
A European Union convention is a formal international agreement between EU member states, or between the EU and other parties, that establishes common rules, standards, or cooperation frameworks in specific policy areas.
-
E.
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.
- 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_69eeeb53939c8190bd431f32b060f01f |
completed | April 27, 2026, 4:51 a.m. |
Created at: April 27, 2026, 7:04 a.m.