Triple
T22404926
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European Union Agency for Fundamental Rights |
E553855
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fundamental rights body |
C13048
|
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: fundamental rights body Context triple: [European Union Agency for Fundamental Rights, instanceOf, fundamental rights body]
-
A.
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.
-
B.
independent human rights institution
chosen
An independent human rights institution is a formally established, autonomous body mandated to promote and protect human rights by monitoring compliance, advising authorities, handling complaints, and raising public awareness free from political or other undue influence.
-
C.
Judicial body
A judicial body is an official group or institution empowered by law to interpret and apply legal rules, resolve disputes, and administer justice.
-
D.
network of national human rights institutions
A network of national human rights institutions is a coordinated system of independent, state-based bodies that collaborate to promote, protect, and strengthen human rights standards and practices domestically and internationally.
-
E.
body of public law
The body of public law is the collection of legal rules and principles that govern the organization, powers, and functions of the state and its relationship with individuals and other public entities.
- 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_69e11e4da7048190b4387d422a9a0de5 |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:46 p.m.