Triple
T10524882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GW SEAS |
E248274
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | school of engineering and applied science |
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: school of engineering and applied science Context triple: [GW SEAS, instanceOf, school of engineering and applied science]
-
A.
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.
-
B.
faculty of science and engineering
The faculty of science and engineering is an academic division within a university that focuses on education and research in scientific and technological disciplines, including natural sciences, mathematics, and various branches of engineering.
-
C.
science and engineering campus
A science and engineering campus is a specialized academic environment that concentrates facilities, laboratories, and resources to support education and research in scientific and engineering disciplines.
-
D.
engineering institute
An engineering institute is an educational and research organization dedicated to teaching, advancing, and applying engineering principles and technologies across various specialized fields.
-
E.
school of architecture
A school of architecture is an educational institution or academic department dedicated to teaching the theory, history, and practice of designing buildings and the built environment.
- 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_69d381c5c7448190bec34bee7ec72bac |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 12:29 p.m.