Triple
T3904297
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greatest Show on Turf offense |
E90567
|
entity |
| Predicate | offensiveStyle |
P3775
|
FINISHED |
| Object | pass-heavy |
—
|
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: pass-heavy | Statement: [Greatest Show on Turf offense, offensiveStyle, pass-heavy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offensiveStyle Context triple: [Greatest Show on Turf offense, offensiveStyle, pass-heavy]
-
A.
offensiveStrategy
Indicates a strategic approach focused on attacking or aggressively advancing against an opponent.
-
B.
offense
Indicates that one entity commits, causes, or is responsible for a violation, wrongdoing, or rule-breaking act against another entity or governing norms.
-
C.
offensiveForce
Indicates the use or application of aggressive or attacking power or violence by one entity against another.
-
D.
offenseNicknamed
Indicates that an offensive unit, team, or strategy is commonly referred to by a particular nickname.
-
E.
styleOfPlay
chosen
Indicates the characteristic manner or approach in which an entity performs or behaves, especially in a game, sport, or artistic context.
- 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_69aed95d315881908cbf1bf4a7215fbf |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef1abe2dc81909c18aeae9b286898 |
completed | March 9, 2026, 4:13 p.m. |
| PD | Predicate disambiguation | batch_69aee75cff148190b6d5979d17fae085 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:22 p.m.