Triple
T27156105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | College of Information Sciences and Technology |
E682522
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | information sciences school |
C4190
|
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: information sciences school Context triple: [College of Information Sciences and Technology, instanceOf, information sciences school]
-
A.
information school
chosen
An information school is an academic institution or department focused on the study, design, and management of information, technology, and people’s interactions with them.
-
B.
computer science school
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.
library and information science school
A library and information science school is an educational institution or academic unit that prepares students to manage, organize, preserve, and provide access to information resources across libraries, archives, and other information environments.
-
D.
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.
-
E.
science and technology school
A science and technology school is an educational institution that focuses on teaching and advancing knowledge in scientific disciplines, engineering, and technological innovation through specialized curricula and hands-on learning.
- 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_69eefaceb2a08190b9659b7f730629f5 |
completed | April 27, 2026, 5:57 a.m. |
Created at: April 27, 2026, 9:16 a.m.