Triple
T32119045
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grace procedure |
E820314
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | university governance procedure |
C39299
|
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 governance procedure Context triple: [Grace procedure, instanceOf, university governance procedure]
-
A.
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.
-
B.
higher education governance document
chosen
A higher education governance document is an official record that defines the structures, roles, rules, and decision-making processes by which a college or university is directed and controlled.
-
C.
governmental procedure
A governmental procedure is a formally established sequence of actions, rules, and decision-making steps that public authorities follow to create, implement, or enforce laws and policies.
-
D.
university statute book
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.
-
E.
governance doctrine
A governance doctrine is a coherent set of principles, rules, and practices that defines how authority is structured, decisions are made, and accountability is maintained within an organization or political system.
- 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_69f34902d42c819083a8e6bba9a8bb9a |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:28 a.m.