Triple
T37544457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rex Ryan’s 3–4 attacking defense |
E933419
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | defensive scheme |
C7644
|
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: defensive scheme Context triple: [Rex Ryan’s 3–4 attacking defense, instanceOf, defensive scheme]
-
A.
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.
-
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.
defensive basketball system
A defensive basketball system is a coordinated set of strategies, formations, and responsibilities designed to prevent the opposing team from scoring by disrupting their offensive plays.
-
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.
defensive measure
chosen
A defensive measure is an action, system, or strategy designed to protect against, reduce, or mitigate harm from potential threats or attacks.
- 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.