Triple
T37238514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | University of São Paulo campus network |
E923647
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | higher education infrastructure system |
C907
|
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: higher education infrastructure system Context triple: [University of São Paulo campus network, instanceOf, higher education infrastructure system]
-
A.
higher education system segment
A higher education system segment is a distinct subset of institutions, programs, or stakeholders within the broader higher education landscape that share common characteristics, functions, or target populations.
-
B.
university system
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.
-
C.
higher education site
A higher education site is an online platform that provides information, resources, and services related to colleges, universities, academic programs, admissions, and campus life for prospective and current students.
-
D.
higher education organization
A higher education organization is an institution that provides post-secondary academic or professional education, conducts research, and grants recognized degrees or certifications.
-
E.
educational infrastructure
chosen
Educational infrastructure encompasses the physical facilities, technological systems, human resources, and organizational structures that support the delivery, management, and improvement of learning and teaching.
- 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_69f76ea9fee88190a589f661d95a7189 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:15 p.m.