Triple
T28556797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Legion of Boom defense era |
E723029
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Seattle Seahawks historical period |
C34626
|
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: Seattle Seahawks historical period Context triple: [Legion of Boom defense era, instanceOf, Seattle Seahawks historical period]
-
A.
Green Bay Packers season
A Green Bay Packers season represents a single year of the franchise’s professional football activities, encompassing all preseason, regular season, and postseason games, team performance, roster changes, and notable events.
-
B.
St. Louis Rams team era
The "St. Louis Rams team era" refers to the period from 1995 to 2015 when the Rams NFL franchise was based in St. Louis, marked by the "Greatest Show on Turf" years, a Super Bowl XXXIV championship, and a distinct local fan and football culture.
-
C.
football team era
chosen
A football team era is a distinct period in a team's history characterized by a relatively stable core of players, coaches, strategies, and achievements that define its identity and performance during that time.
-
D.
Kansas City Chiefs season
A Kansas City Chiefs season represents a single year of the franchise’s professional football activities, encompassing all preseason, regular season, and postseason games, player and staff changes, and team performance outcomes.
-
E.
New York Jets era
New York Jets era: A period in NFL history defined by the performance, culture, and organizational developments of the New York Jets franchise during a specific span of seasons.
- 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_69f01a60204481909af1bb76247b8221 |
completed | April 28, 2026, 2:24 a.m. |
Created at: April 28, 2026, 3:46 a.m.