Triple
T30385866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oregon School Activities Association |
E772952
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | governing body for school activities |
C42598
|
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: governing body for school activities Context triple: [Oregon School Activities Association, instanceOf, governing body for school activities]
-
A.
scholastic activities governing body
A scholastic activities governing body is an organization that oversees, regulates, and promotes extracurricular academic and co-curricular programs, such as competitions and clubs, within educational institutions.
-
B.
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.
-
C.
high school athletics governing body
chosen
A high school athletics governing body is an organization that sets and enforces rules, eligibility standards, and competition structures for interscholastic sports within a defined region or jurisdiction.
-
D.
educational institution governing body
A group or organization responsible for overseeing, directing, and making policy decisions for an educational institution or system.
-
E.
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.
- 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_69f2248ef0a48190aa54d4d8ac3e5758 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 8:01 p.m.