Triple
T384712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heinz College of Information Systems and Public Policy |
E8755
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | school of information systems |
C1069
|
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: school of information systems Context triple: [Heinz College of Information Systems and Public Policy, instanceOf, school of information systems]
-
A.
information system
An information system is an organized combination of people, processes, data, and technology designed to collect, process, store, and distribute information to support decision-making and control in an organization.
-
B.
computer science school
chosen
A computer science school is an educational institution or program dedicated to teaching the principles, theories, and practical skills of computing, programming, and information technology.
-
C.
humanities and social sciences school
A humanities and social sciences school is an academic institution or division dedicated to the study, teaching, and research of disciplines that examine human culture, society, behavior, and thought, such as history, literature, philosophy, sociology, and political science.
-
D.
university
A university is an institution of higher education and research that grants academic degrees and fosters advanced learning across diverse fields of study.
-
E.
private university
A private university is a higher education institution that is independently funded and operated, primarily through tuition, donations, and endowments rather than direct government support.
- 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_69a2e7f47dd08190a4e294ccbbe46cd4 |
completed | Feb. 28, 2026, 1:04 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.