Triple
T28388328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Europol Management Board |
E719083
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | EU agency body |
C46234
|
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 agency body Context triple: [Europol Management Board, instanceOf, EU agency body]
-
A.
European Union body
A European Union body is an institution, agency, or other organizational entity established by the EU’s founding treaties or secondary legislation to perform specific political, regulatory, advisory, or administrative functions within the Union’s governance framework.
-
B.
organ of the European Union agency
chosen
An organ of a European Union agency is a formally established internal body, such as a management board or executive director, that exercises specific decision-making, supervisory, or advisory functions within that agency’s institutional framework.
-
C.
specialised EU agency
A specialised EU agency is a decentralized body of the European Union created by legislation to perform specific technical, scientific, or operational tasks that support EU policies and decision-making in a particular domain.
-
D.
European organisation
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.
-
E.
EU–US body
A formal, institutionalized entity that facilitates structured political, economic, and regulatory dialogue and cooperation between the European Union and the United 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_69eff6ef211081909d31d9be5f5567e6 |
completed | April 27, 2026, 11:53 p.m. |
Created at: April 28, 2026, 1:11 a.m.