Triple
T22615562
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NCAA Football Rules and Interpretations |
E558136
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | college football rules code |
C27776
|
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: college football rules code Context triple: [NCAA Football Rules and Interpretations, instanceOf, college football rules code]
-
A.
American football rules
chosen
American football rules define the structured guidelines governing gameplay, scoring, player conduct, and officiating in organized American football competitions.
-
B.
college football
College football is a competitive team sport played by student-athletes representing colleges and universities, featuring organized seasons, conferences, and championship games that are central to campus culture and regional traditions.
-
C.
college football designation
A college football designation is a categorical label that classifies teams, players, or programs based on factors such as division, conference, eligibility, or competitive status within the collegiate football system.
-
D.
college football student section
A college football student section is the designated area in a stadium where enrolled students gather to enthusiastically support their team with coordinated chants, cheers, and school spirit.
-
E.
college football backfield
The college football backfield is the group of offensive players lined up behind or near the quarterback—typically including running backs and sometimes fullbacks—responsible for rushing, receiving, and pass protection.
- 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_69e24545a8e08190bfa7482a2c725ff1 |
completed | April 17, 2026, 2:35 p.m. |
Created at: April 17, 2026, 2:59 p.m.