Triple
T26968530
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CERN experimental programme |
E679239
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | scientific research programme |
C52310
|
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 research programme Context triple: [CERN experimental programme, instanceOf, scientific research programme]
-
A.
scientific research support program
A scientific research support program is an organized initiative that provides resources, funding, infrastructure, and guidance to facilitate the planning, execution, and dissemination of scientific studies.
-
B.
university research program
A university research program is an organized, often interdisciplinary initiative within a higher education institution that supports systematic investigation, innovation, and scholarly inquiry in specific fields or themes.
-
C.
research center program
A research center program is an organized initiative within a research institution that coordinates projects, resources, and collaborations to advance inquiry and innovation in a specific field or set of related disciplines.
-
D.
research project
A research project is a structured, systematic investigation designed to answer specific questions or test hypotheses by collecting, analyzing, and interpreting data within a defined scope and timeframe.
-
E.
international scientific programme
An international scientific programme is a coordinated, long-term research initiative involving multiple countries and institutions that collaboratively address shared scientific questions or global challenges.
- 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_69eeeb4f3a448190b1e94b2d4776c16e |
completed | April 27, 2026, 4:51 a.m. |
Created at: April 27, 2026, 6:37 a.m.