Triple
T13142975
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tampa Bay Storm |
E312257
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Arena Football League team |
C22566
|
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: Arena Football League team Context triple: [Tampa Bay Storm, instanceOf, Arena Football League team]
-
A.
Alliance of American Football team
An Alliance of American Football team is a professional American football franchise that competed in the short-lived Alliance of American Football league, representing a specific city or region with its own roster, coaching staff, and branding.
-
B.
arena football team
chosen
An arena football team is a professional or semi-professional American football organization that competes in indoor arenas under modified rules designed for a smaller field and faster-paced, high-scoring games.
-
C.
United States Football League team
A United States Football League team is a professional American football franchise that competes in the USFL, representing a specific city or region and consisting of players, coaches, and staff organized to participate in league games and championships.
-
D.
Arena Football League division
An Arena Football League division is a grouping of teams within the Arena Football League organized for the purposes of scheduling, competition, and determining playoff qualification.
-
E.
United Football League team
A United Football League team is a professional American football franchise that competes in the United Football League, representing a specific city or region with its own roster, coaching staff, and branding.
- 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_69d806aabde48190899e13e41659cae5 |
completed | April 9, 2026, 8:06 p.m. |
Created at: April 9, 2026, 9:10 p.m.