Triple
T7920415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Johns Hopkins University campus network |
E183930
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | multi-campus system |
C8236
|
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: multi-campus system Context triple: [Johns Hopkins University campus network, instanceOf, multi-campus system]
-
A.
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.
-
B.
multi-campus university structure
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.
-
C.
university system
chosen
A university system is an integrated organizational framework that manages academic programs, students, faculty, resources, and administrative processes across one or more higher education institutions.
-
D.
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.
-
E.
collegiate university system
A collegiate university system is a higher education structure in which a central university is composed of semi-autonomous constituent colleges that share academic standards and degrees while maintaining their own governance, finances, and community life.
- 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_69ca828efbe48190bd48482650182e79 |
completed | March 30, 2026, 2:02 p.m. |
Created at: March 30, 2026, 5:06 p.m.