Triple
T5766907
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CERN-ISOLDE collaboration |
E127237
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | scientific research collaboration |
C343
|
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 collaboration Context triple: [CERN-ISOLDE collaboration, instanceOf, scientific research collaboration]
-
A.
university collaboration
University collaboration is the structured partnership between universities and external entities (such as other academic institutions, industry, government, or communities) to jointly pursue research, education, innovation, and resource sharing.
-
B.
research consortium
chosen
A research consortium is a collaborative alliance of multiple organizations or institutions that pool resources, expertise, and infrastructure to conduct joint research toward shared scientific or technological goals.
-
C.
research network
A research network is a structured system of interconnected researchers, institutions, and resources that collaboratively generate, share, and advance knowledge within and across disciplines.
-
D.
scientific endeavor
A scientific endeavor is a systematic, evidence-based pursuit aimed at discovering, explaining, and predicting natural or social phenomena through observation, experimentation, and critical analysis.
-
E.
scientific research field
A scientific research field is a systematically organized area of study focused on investigating specific phenomena, principles, or questions using established scientific methods and theoretical frameworks.
- 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_69c00834f6308190851b0abeddd8ed7e |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 3:49 p.m.