Triple
T26627344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Purdue Polytechnic statewide locations |
E668390
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | network of branch campuses |
C41837
|
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: network of branch campuses Context triple: [Purdue Polytechnic statewide locations, instanceOf, network of branch campuses]
-
A.
multi-campus educational network
chosen
A multi-campus educational network is an interconnected system of geographically distributed campuses that share academic programs, resources, governance, and support services to deliver coordinated, high-quality education across multiple locations.
-
B.
network of universities
A network of universities is an interconnected system of higher education institutions that collaborate to share resources, research, programs, and expertise across organizational and geographic boundaries.
-
C.
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.
-
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.
multi-campus college
A multi-campus college is an educational institution that operates across multiple geographically separate locations under a single administrative and academic system.
- 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_69ee9cff507c819092b95bf7219a702e |
completed | April 26, 2026, 11:17 p.m. |
Created at: April 27, 2026, 2:23 a.m.