Triple
T760023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Department of Mechanical Engineering (Carnegie Mellon University) |
E16046
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | engineering department |
C4189
|
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 department Context triple: [Department of Mechanical Engineering (Carnegie Mellon University), instanceOf, engineering department]
-
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.
college of engineering
chosen
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.
-
C.
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.
-
D.
engineering standard
An engineering standard is a documented set of agreed-upon technical criteria, methods, and requirements intended to ensure safety, interoperability, quality, and consistency in engineering design, production, and operation.
-
E.
engineering designation
An engineering designation is a formal title or credential that identifies an engineer’s professional qualification, specialization, and level of responsibility within the engineering field.
- 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_69a493684ee48190bd43b7c78da4aec8 |
completed | March 1, 2026, 7:28 p.m. |
Created at: March 1, 2026, 7:37 p.m.