Triple
T15249202
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | School of Engineering and Informatics |
E364471
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | school of the University of Sussex |
C36357
|
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 the University of Sussex Context triple: [School of Engineering and Informatics, instanceOf, school of the University of Sussex]
-
A.
University of York
The University of York is a collegiate research university in York, England, known for its strong academic reputation, interdisciplinary focus, and modern campus set in extensive parkland.
-
B.
college of the University of London
A college of the University of London is a semi-autonomous higher education institution that forms part of the federal University of London, delivering its own teaching and research while contributing to the university’s overall academic framework.
-
C.
college of Lancaster University
A college of Lancaster University is a semi-autonomous community within the university that provides students and staff with social, residential, and pastoral support, fostering identity and belonging alongside academic life.
-
D.
college of the University of York
A college of the University of York is a semi-autonomous community within the university that provides residential, social, pastoral, and academic support to its members.
-
E.
school of the University of Cambridge
A school of the University of Cambridge is an administrative grouping of related faculties and departments that coordinates academic strategy, governance, and resource allocation within a broad disciplinary area of the university.
- F. None of above. chosen
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_69d85a0dde7481908fc64d1e82d5d20d |
completed | April 10, 2026, 2:01 a.m. |
Created at: April 10, 2026, 3:13 a.m.