Triple
T20655963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tampa 2 defensive scheme |
E507626
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | zone coverage defense |
C32421
|
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: zone coverage defense Context triple: [Tampa 2 defensive scheme, instanceOf, zone coverage defense]
-
A.
defensive play
chosen
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.
-
B.
defensive position
A defensive position is a strategically chosen and prepared location from which forces protect themselves and resist or repel an opponent’s attack.
-
C.
cornerback
A cornerback is a defensive football player responsible for covering wide receivers, defending against passes, and supporting run defense on the edges of the field.
-
D.
defensive line
The defensive line is the group of players positioned at the line of scrimmage whose primary role is to disrupt the offense by stopping running plays and pressuring the quarterback.
-
E.
protective zone
A protective zone is a designated area or boundary established to shield people, assets, or environments from potential harm, hazards, or unauthorized influence.
- 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_69e0b4bf58c081908e52a4500e03ff83 |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:43 a.m.