Triple
T2320721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cambridge Engineering Design Centre |
E51172
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | engineering research group |
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: engineering research group Context triple: [Cambridge Engineering Design Centre, instanceOf, engineering research group]
-
A.
engineering division
The engineering division is an organizational unit responsible for designing, developing, and maintaining technical systems, products, and infrastructure within a company or institution.
-
B.
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.
-
C.
research consortium
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.
-
D.
engineering library
An engineering library is a specialized collection of technical resources, including books, journals, standards, and digital tools, that support research, education, and practice in engineering disciplines.
-
E.
college of engineering
A college of engineering is an academic division within a university that offers specialized education and research programs in various engineering disciplines, preparing students for professional engineering careers and technological innovation.
- 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_69a88b074b908190ae983dbca7757d88 |
completed | March 4, 2026, 7:41 p.m. |
Created at: March 4, 2026, 7:49 p.m.