Triple
T4750114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Long Beach State 49ers football team |
E105456
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | defunct college football program |
C51
|
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: defunct college football program Context triple: [Long Beach State 49ers football team, instanceOf, defunct college football program]
-
A.
university football team
A university football team is an organized group of student-athletes representing their institution in competitive American football, typically governed by collegiate athletic associations and supported by the campus community.
-
B.
former college
A former college is an educational institution that once operated as a college but has since closed, merged, or been reclassified, and no longer functions in its original capacity.
-
C.
college football organization
A college football organization is an entity that governs, coordinates, and promotes intercollegiate football programs, overseeing competition rules, scheduling, eligibility, and related administrative and developmental activities.
-
D.
college athletic program
chosen
A college athletic program is an organized set of sports teams, resources, and support services sponsored by a college or university to provide competitive and recreational athletic opportunities for its students.
-
E.
college football tradition
A college football tradition is a recurring, culturally significant practice or ritual associated with a team, game day, or fan base that reinforces school identity, community, and continuity over time.
- 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_69bd43f07fa48190954317d01600994a |
completed | March 20, 2026, 12:56 p.m. |
Created at: March 20, 2026, 1:20 p.m.