Triple
T26509705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | scientific operations directorate |
E669645
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | science management 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 management body Context triple: [scientific operations directorate, instanceOf, science management 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 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.
-
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.
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.
-
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. 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_69eeb319ec70819090834c2591cf5f1e |
completed | April 27, 2026, 12:51 a.m. |
Created at: April 27, 2026, 1:19 a.m.