Triple
T3850370
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bauman Moscow State Technical University (branches) |
E85280
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | university branch network |
C8237
|
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 branch network Context triple: [Bauman Moscow State Technical University (branches), instanceOf, university branch network]
-
A.
school network
A school network is a connected system of schools, resources, and stakeholders that collaborates to share information, coordinate activities, and support educational goals across multiple institutions.
-
B.
university satellite campus
A university satellite campus is a geographically separate branch of a main university that offers selected academic programs and services to extend access to higher education in a different location.
-
C.
multi-campus university structure
chosen
A multi-campus university structure is an organizational framework in which a single university operates multiple geographically dispersed campuses that share governance, academic standards, and resources while serving distinct local communities and programmatic needs.
-
D.
multi-campus university
A multi-campus university is an institution of higher education that operates multiple geographically separate campuses under a single administrative and academic governance structure.
-
E.
public central university
A public central university is a government-funded higher education institution established and administered by a national or federal authority, typically offering a wide range of academic programs and research opportunities.
- 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_69aed936de1c81908f91bed80f70abb2 |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:19 p.m.