Triple
T22393589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rio Hondo Community College District |
E553572
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public education governing body |
C8555
|
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 education governing body Context triple: [Rio Hondo Community College District, instanceOf, public education governing body]
-
A.
school governing body
A school governing body is a group of elected and appointed individuals responsible for setting the strategic direction, policies, and oversight of a school’s management and performance.
-
B.
education policy body
An education policy body is an organization or governing entity responsible for developing, overseeing, and evaluating policies and regulations that shape the structure, standards, and operation of an education system.
-
C.
school district governing body
A school district governing body is an elected or appointed group responsible for setting policies, overseeing budgets, and guiding the overall direction and accountability of the public schools within a specific district.
-
D.
school board
chosen
A school board is a governing body of elected or appointed members responsible for setting policies, overseeing budgets, and guiding the strategic direction of a school district.
-
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_69e11e4cf87c8190a1ff474daec326b7 |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:45 p.m.