Triple
T10600006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ten-Year War |
E275717
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | college football rivalry period |
C28691
|
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 rivalry period Context triple: [Ten-Year War, instanceOf, college football rivalry period]
-
A.
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.
-
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 basketball rivalry
A college basketball rivalry is a recurring, highly competitive series of games between two collegiate teams characterized by historical significance, regional or conference proximity, and intense fan and media interest.
-
D.
college football division
A college football division is a grouping of college football teams, typically within a conference or organizational tier, that compete against each other under shared rules, schedules, and championship structures.
-
E.
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.
- F. None of above. chosen
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_69d6aaf948d88190806cc3a8c47a3fb2 |
completed | April 8, 2026, 7:22 p.m. |
Created at: April 8, 2026, 7:30 p.m.