Triple
T22318748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | University Interscholastic League |
E551723
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | interscholastic activities association |
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: interscholastic activities association Context triple: [University Interscholastic League, instanceOf, interscholastic activities association]
-
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.
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.
-
C.
intercollegiate athletic events
Intercollegiate athletic events are organized sports competitions in which teams or individuals representing different colleges or universities compete under established rules and governing bodies.
-
D.
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.
-
E.
extracurricular activity
An extracurricular activity is a structured, voluntary pursuit outside regular academic coursework that supports personal, social, or skill development, such as clubs, sports, arts, or community service.
- 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.