Triple
T996124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MIT Department of Aeronautics and Astronautics |
E21498
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | aerospace 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: aerospace engineering department Context triple: [MIT Department of Aeronautics and Astronautics, instanceOf, aerospace engineering department]
-
A.
aerospace engineer
An aerospace engineer is a professional who designs, develops, tests, and improves aircraft, spacecraft, satellites, and related systems to ensure safe, efficient, and reliable flight within and beyond Earth’s atmosphere.
-
B.
aerospace corporation
An aerospace corporation is a large-scale enterprise that designs, manufactures, and services aircraft, spacecraft, and related systems and technologies for commercial, military, and space applications.
-
C.
aerospace expert
An aerospace expert is a highly skilled professional with deep knowledge of aeronautics and astronautics who designs, analyzes, and optimizes aircraft, spacecraft, and related systems for performance, safety, and reliability.
-
D.
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.
-
E.
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.
- 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_69a493c476b48190b41fc5e793171cc6 |
completed | March 1, 2026, 7:30 p.m. |
Created at: March 1, 2026, 7:41 p.m.