Triple
T7422887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CERN Technology Department |
E171292
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | research and development unit |
C425
|
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: research and development unit Context triple: [CERN Technology Department, instanceOf, research and development unit]
-
A.
research and development organization
chosen
A research and development organization is an entity dedicated to systematically investigating ideas and technologies to create new knowledge, products, or processes and improve existing ones.
-
B.
multidisciplinary research unit
A multidisciplinary research unit is an organized group that integrates expertise, methods, and perspectives from multiple academic or professional fields to collaboratively investigate complex problems and generate comprehensive insights.
-
C.
research facility
A research facility is a specialized institution equipped with laboratories, instruments, and resources where scientists and experts systematically investigate, experiment, and develop new knowledge or technologies.
-
D.
division of a national research institute
A division of a national research institute is a specialized organizational unit responsible for conducting and coordinating research, development, and related activities within a defined scientific or technical domain under the institute’s broader mission.
-
E.
research ministry
A research ministry is a governmental or organizational body responsible for overseeing, funding, and guiding scientific and technological research to support policy, innovation, and societal development.
- 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_69c68a625d048190af70eb8b63bec5a0 |
completed | March 27, 2026, 1:47 p.m. |
Created at: March 27, 2026, 3:12 p.m.