Triple
T3502695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1940 NFL Championship Game |
E74003
|
entity |
| Predicate | featuredOffensiveScheme |
P25454
|
FINISHED |
| Object | T-formation |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: T-formation | Statement: [1940 NFL Championship Game, featuredOffensiveScheme, T-formation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuredOffensiveScheme Context triple: [1940 NFL Championship Game, featuredOffensiveScheme, T-formation]
-
A.
offensiveStrategy
chosen
Indicates a strategic approach focused on attacking or aggressively advancing against an opponent.
-
B.
defensivePlan
Indicates a relationship where an entity formulates or adopts a strategy specifically intended to protect against threats, attacks, or other adverse actions.
-
C.
offensiveCoordinatorAtStart
Indicates that the person served as the offensive coordinator of a team at the beginning of a specified season or time period.
-
D.
offensiveForce
Indicates the use or application of aggressive or attacking power or violence by one entity against another.
-
E.
decidingPlayOffenseTeam
Indicates that an entity is choosing or determining which team will play on offense.
- F. None of above.
Provenance (3 batches)
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_69ad85ce7a9c81909ddc5cf0cb67a6e3 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbbef47988190b5b3fe2e452b9ac8 |
completed | March 8, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_69adae0cd8b0819099da300af09880da |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:18 p.m.