Triple
T32564224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Statutes of the University of Southampton |
E832311
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | university statutes |
C21990
|
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: university statutes Context triple: [Statutes of the University of Southampton, instanceOf, university statutes]
-
A.
university statute book
chosen
A university statute book is an official compilation of the institution’s fundamental rules, regulations, and governance provisions that define its structure, authorities, and procedures.
-
B.
university establishment act
A university establishment act is a formal legislative or governmental instrument that legally creates a university, defining its powers, governance structure, objectives, and regulatory framework.
-
C.
university charter
A university charter is a formal legal document that establishes a university’s existence, defines its mission, governance structure, and powers, and grants it the authority to operate and confer degrees.
-
D.
university governing body
A university governing body is a formal group of appointed or elected individuals responsible for setting the institution’s strategic direction, overseeing its policies and finances, and ensuring accountability and compliance with legal and educational standards.
-
E.
university legal office
A university legal office is the department responsible for providing legal advice, ensuring regulatory compliance, managing contracts, and handling disputes and risk management on behalf of the institution.
- 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_69f34927bb308190ad94da1b11cad13c |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 1:03 a.m.