Triple
T22318750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | University Interscholastic League |
E551723
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | governing body for school competitions |
C40664
|
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 competitions Context triple: [University Interscholastic League, instanceOf, governing body for school competitions]
-
A.
high school athletics governing body
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.
-
B.
scholastic activities governing body
chosen
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.
-
C.
student sports body
A student sports body is an organized group of student representatives responsible for promoting, coordinating, and managing sports and athletic activities within an educational institution.
-
D.
sports governing committee
A sports governing committee is an organized body responsible for setting rules, overseeing competitions, and making policy decisions to regulate and promote a particular sport or group of sports.
-
E.
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.
- 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_69e11e4776588190abb21e5cea79973f |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:42 p.m.