Triple
T7134715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | University of Alaska Board of Regents |
E166276
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public governing body |
C3213
|
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 governing body Context triple: [University of Alaska Board of Regents, instanceOf, public governing body]
-
A.
governing body
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.
governing council
A governing council is a formal body of appointed or elected individuals responsible for making high-level decisions, setting policies, and providing oversight for an organization, community, or institution.
-
C.
governing body members
Individuals who hold official positions within a governing body and are responsible for making, interpreting, or enforcing policies and decisions on behalf of an organization, community, or state.
-
D.
public administration body
chosen
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.
-
E.
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.
- 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_69c68884a9388190af42f90d1c1a7151 |
completed | March 27, 2026, 1:39 p.m. |
Created at: March 27, 2026, 2:45 p.m.