Triple
T37544458
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rex Ryan’s 3–4 attacking defense |
E933419
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | NFL defensive scheme |
C12231
|
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: NFL defensive scheme Context triple: [Rex Ryan’s 3–4 attacking defense, instanceOf, NFL defensive scheme]
-
A.
NFL offensive system
An NFL offensive system is the overarching strategic framework that defines how a team structures, calls, and executes its plays to move the ball and score, integrating schemes, terminology, player roles, and situational tactics.
-
B.
NFL offense
An NFL offense is the unit of a football team responsible for advancing the ball and scoring points through coordinated plays involving the quarterback, linemen, and skill-position players.
-
C.
American football offense
The American football offense is the team unit responsible for advancing the ball downfield through coordinated plays—running, passing, and strategic formations—with the goal of scoring points against the opposing defense.
-
D.
American football defensive unit
chosen
The American football defensive unit is the group of players on a team responsible for preventing the opposing offense from advancing the ball and scoring, primarily through tackling, pass coverage, and creating turnovers.
-
E.
defensive play
Defensive play is a strategic approach in games or sports focused on preventing the opponent from scoring or gaining advantage, often by prioritizing protection, positioning, and risk minimization over aggressive advancement.
- 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_69f76eca55bc8190acf25741793d5dac |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:17 p.m.