Triple
T36638651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European Network of Public Employment Services |
E904526
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | EU 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: EU network Context triple: [European Network of Public Employment Services, instanceOf, EU network]
-
A.
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.
-
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.
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.
-
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 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_69f76e6c63e48190b1d0c3a79a6c7406 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:11 p.m.