Triple
T37686810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. Anthony Friars |
E938389
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | high school basketball program |
C12266
|
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: high school basketball program Context triple: [St. Anthony Friars, instanceOf, high school basketball program]
-
A.
high school athletic program
chosen
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.
-
B.
high school boys' basketball team
A high school boys' basketball team is a group of male student-athletes representing their school in organized basketball practices, competitions, and related activities under the guidance of a coach.
-
C.
collegiate basketball team
A collegiate basketball team is an organized group of student-athletes representing a college or university in competitive basketball, adhering to institutional and league rules while balancing academics and athletics.
-
D.
basketball academy
A basketball academy is an organized training institution that develops players’ skills, physical conditioning, and game understanding through structured coaching programs and competitive play.
-
E.
university basketball team
A university basketball team is an organized group of student-athletes representing their institution in competitive collegiate basketball, balancing academic responsibilities with training, teamwork, and intercollegiate games.
- 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_69f76ed881408190bc62a969530a4a53 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:18 p.m.