Triple
T7190059
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moscow School of Management Skolkovo (design contribution) |
E167668
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | university campus design |
C193
|
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: university campus design Context triple: [Moscow School of Management Skolkovo (design contribution), instanceOf, university campus design]
-
A.
university campus building
A university campus building is a physical structure within a university’s grounds designed to support academic, administrative, residential, or recreational functions for students, faculty, and staff.
-
B.
campus
A campus is a defined area of land that houses the buildings, facilities, and open spaces of an educational institution, supporting academic, residential, and social activities.
-
C.
university campus area
chosen
A university campus area is the designated physical environment of a university, encompassing academic buildings, student housing, recreational facilities, green spaces, and supporting infrastructure where educational and social activities occur.
-
D.
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.
-
E.
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.
- 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_69c6888b5248819090499a884ee3ec39 |
completed | March 27, 2026, 1:39 p.m. |
Created at: March 27, 2026, 2:50 p.m.