Triple
T37732804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Department of Basic Research |
E940205
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | science administration 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: science administration body Context triple: [Department of Basic Research, instanceOf, science administration body]
-
A.
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.
-
B.
public administration body
A public administration body is an organization within the public sector responsible for implementing laws, delivering public services, and managing governmental policies and resources on behalf of the state and its citizens.
-
C.
science agency
A science agency is an organization, typically governmental or intergovernmental, that funds, coordinates, and oversees scientific research and development to advance knowledge and inform policy.
-
D.
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.
-
E.
public administration
Public administration is the field and practice of implementing government policies, managing public programs, and coordinating resources and personnel to serve the public interest and promote effective governance.
- 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_69f76edefd048190a32212c5c3919531 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:18 p.m.