Triple
T33010658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reich Research Council |
E844636
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | scientific coordinating body |
C51670
|
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: scientific coordinating body Context triple: [Reich Research Council, instanceOf, scientific coordinating body]
-
A.
science policy coordination body
A science policy coordination body is an organization that aligns scientific research, evidence, and expertise with policymaking processes across institutions and sectors to ensure coherent, informed, and effective public policy.
-
B.
science management body
chosen
A science management body is an organization or committee responsible for planning, coordinating, overseeing, and evaluating scientific research activities, resources, and policies within a defined scope or institution.
-
C.
regional scientific body
A regional scientific body is an organization that coordinates, supports, and promotes scientific research, collaboration, and policy advice within a specific geographic region.
-
D.
scientific committee
A scientific committee is a group of experts who collaboratively evaluate, guide, and make decisions on scientific matters, such as research quality, funding, ethics, and strategic priorities.
-
E.
scientific community organization
A scientific community organization is a structured group that unites researchers and professionals within specific scientific fields to promote collaboration, knowledge exchange, standard-setting, and advancement of the discipline.
- 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_69f3494f3b4081909dccf2af34372a26 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:23 a.m.