Triple
T32761376
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mississippi High School Activities Association |
E837764
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | governing body for high school sports |
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 high school sports Context triple: [Mississippi High School Activities Association, instanceOf, governing body for high school sports]
-
A.
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.
-
B.
high school athletic conference
A high school athletic conference is an organized group of secondary schools that regularly compete against each other in interscholastic sports under shared rules, schedules, and governance.
-
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.
high school athletic program
A high school athletic program is an organized set of school-sponsored sports teams, activities, and support services designed to promote student physical fitness, skill development, teamwork, and school spirit through structured competition and training.
-
E.
high school sports competition
A high school sports competition is an organized event where student athletes from one or more schools compete in structured athletic contests governed by standardized rules and regulations.
- 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_69f34939857c8190aa9970c51feec1eb |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:13 a.m.