Triple
T13626632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baltimore Colts offense |
E325599
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | American football offensive unit |
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 unit Context triple: [Baltimore Colts offense, instanceOf, American football offensive unit]
-
A.
American football defensive unit
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.
-
B.
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.
-
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.
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.
-
E.
American football player
An American football player is an athlete who participates in the sport of American football, executing specialized offensive, defensive, or special teams roles within an organized team structure.
- 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_69d8076aae28819092cf636190ee5529 |
completed | April 9, 2026, 8:09 p.m. |
Created at: April 9, 2026, 9:51 p.m.