Triple
T20897562
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Board of Governors of the University of Lethbridge |
E514579
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public sector governance body |
C172
|
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: public sector governance body Context triple: [Board of Governors of the University of Lethbridge, instanceOf, public sector governance body]
-
A.
governing body
chosen
A governing body is an organized group of individuals with the authority and responsibility to make decisions, set policies, and oversee the direction and management of an institution, community, or state.
-
B.
public administration body
A public administration body is an organization within the public sector responsible for implementing laws, delivering public services, and managing governmental policies and resources on behalf of the state and its citizens.
-
C.
governance entity
A governance entity is an individual, group, or organization with the authority and responsibility to establish, oversee, and enforce rules, policies, and decisions within a defined domain.
-
D.
sectoral policy organ
A sectoral policy organ is an institutional body responsible for formulating, coordinating, and overseeing policies within a specific economic or social sector, such as health, education, or agriculture.
-
E.
proposed governmental body
A proposed governmental body is a conceptual organization suggested to perform specific public functions or governance roles, but which has not yet been formally established or granted legal authority.
- 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_69e0b4f7ebe48190952a85547a0f31a1 |
completed | April 16, 2026, 10:07 a.m. |
Created at: April 16, 2026, 12:47 p.m.