Triple
T3435901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2008 Oregon–Oregon State football game |
E72449
|
entity |
| Predicate | offensiveStyleAway |
P3775
|
FINISHED |
| Object | spread offense |
—
|
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: spread offense | Statement: [2008 Oregon–Oregon State football game, offensiveStyleAway, spread offense]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offensiveStyleAway Context triple: [2008 Oregon–Oregon State football game, offensiveStyleAway, spread offense]
-
A.
offensiveStrategy
Indicates a strategic approach focused on attacking or aggressively advancing against an opponent.
-
B.
styleOfPlay
chosen
Indicates the characteristic manner or approach in which an entity performs or behaves, especially in a game, sport, or artistic context.
-
C.
offensiveForce
Indicates the use or application of aggressive or attacking power or violence by one entity against another.
-
D.
managerAwayTeam
Indicates that a person serves as the manager (coach/head coach) of the away team in a given match or event.
-
E.
offenseNicknamed
Indicates that an offensive unit, team, or strategy is commonly referred to by a particular nickname.
- 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_69ad85af50288190a854b76653deee6f |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb9f2e4b4819085336fb539daf3c7 |
completed | March 8, 2026, 6:03 p.m. |
| PD | Predicate disambiguation | batch_69adae00ad588190bef24373b58a2e1a |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:16 p.m.