Triple
T36639328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Legal Service of the European Commission |
E904541
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | central legal advisory body |
C655
|
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: central legal advisory body Context triple: [Legal Service of the European Commission, instanceOf, central legal advisory body]
-
A.
intergovernmental legal body
An intergovernmental legal body is an organization formed by multiple governments to develop, interpret, or oversee the implementation of international legal norms, agreements, and dispute-resolution mechanisms.
-
B.
central policymaking organ
A central policymaking organ is the primary authoritative body within an organization or state responsible for formulating, coordinating, and directing overarching policies and strategic decisions.
-
C.
cabinet-level body
A cabinet-level body is a high-ranking executive group, typically composed of heads of major government departments and key advisors, that assists a head of state or government in making and implementing national policy decisions.
-
D.
governing body
A governing body is an organized group of individuals with the authority and responsibility to make decisions, set policies, and oversee the direction and management of an institution, community, or state.
-
E.
advisory body
chosen
An advisory body is a group of appointed or elected individuals that provides expert guidance, recommendations, and informed opinions to decision-makers without having formal authority to implement decisions.
- 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.