Triple
T11008080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leibniz Senate |
E260172
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | organ of the Leibniz Association |
C29008
|
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: organ of the Leibniz Association Context triple: [Leibniz Senate, instanceOf, organ of the Leibniz Association]
-
A.
Leibniz Association member
A Leibniz Association member is a research institution or museum in Germany that belongs to the Leibniz Association, collaborating across disciplines to address socially relevant scientific questions.
-
B.
Helmholtz Association of German Research Centres
The Helmholtz Association of German Research Centres is Germany’s largest scientific organization, uniting national research centers to address major societal, scientific, and technological challenges through long-term, large-scale research.
-
C.
organ of the European Research Council
An organ of the European Research Council is a formal governing or advisory body within the ERC’s institutional structure that is responsible for strategic decision-making, oversight, or implementation of its research funding activities.
-
D.
organ of the League of European Research Universities
An organ of the League of European Research Universities is a formal governing or advisory body within the association that is responsible for specific decision-making, coordination, or oversight functions.
-
E.
library association
A library association is an organized group that supports, advocates for, and advances the interests, standards, and professional development of libraries and library workers.
- F. None of above. chosen
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_69d6aa9687448190b28d353b1b6a610e |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:25 p.m.