Triple
T21475085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European Strategy Group |
E529838
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | particle physics policy body |
C26632
|
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: particle physics policy body Context triple: [European Strategy Group, instanceOf, particle physics policy body]
-
A.
particle physics collaboration
A particle physics collaboration is a large, often international team of scientists, engineers, and institutions that jointly design, build, operate, and analyze experiments to study fundamental particles and their interactions.
-
B.
science policy coordination body
chosen
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.
-
C.
CERN governance category
A CERN governance category is a classification that defines the roles, responsibilities, and decision-making authority of organizational bodies within CERN’s institutional and administrative structure.
-
D.
science and technology policy committee
A science and technology policy committee is a group that evaluates, advises on, and helps shape policies and strategies related to scientific research, technological development, and their societal impacts.
-
E.
particle physics model
A particle physics model is a theoretical framework that describes the fundamental particles and their interactions, aiming to explain and predict phenomena at the smallest scales of matter and energy.
- 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_69e0c459acb481909bb6ee452a0045c7 |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:19 p.m.