Triple
T27111521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | West Coast offense |
E686725
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | American football offensive scheme |
C14550
|
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: American football offensive scheme Context triple: [West Coast offense, instanceOf, American football offensive scheme]
-
A.
American football offense
chosen
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.
-
B.
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.
-
C.
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.
-
D.
American football tactical milestone
An American football tactical milestone is a significant strategic achievement or innovation within a game or season—such as a pivotal play, formation, or adjustment—that meaningfully advances a team’s competitive position or influences the evolution of the sport’s tactics.
-
E.
American football play
An American football play is a pre-planned, coordinated sequence of actions executed by the offense or defense from the snap to the end of the down to advance the ball, score, or prevent scoring.
- 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_69ef148accd48190b6ed6e13a15f2a4f |
completed | April 27, 2026, 7:47 a.m. |
Created at: April 27, 2026, 8:54 a.m.