Triple
T4632377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Super Bowl XXXIV |
E101445
|
entity |
| Predicate | winningTeamOffenseStyle |
P3775
|
FINISHED |
| Object | high-powered passing 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: high-powered passing offense | Statement: [Super Bowl XXXIV, winningTeamOffenseStyle, high-powered passing offense]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: winningTeamOffenseStyle Context triple: [Super Bowl XXXIV, winningTeamOffenseStyle, high-powered passing offense]
-
A.
styleOfPlay
chosen
Indicates the characteristic manner or approach in which an entity performs or behaves, especially in a game, sport, or artistic context.
-
B.
winningTeam
Indicates which team is the victor in a given competition, game, or contest.
-
C.
offensiveStrategy
Indicates a strategic approach focused on attacking or aggressively advancing against an opponent.
-
D.
winsWithTeam
Indicates that an entity achieves a victory as a member of, or in conjunction with, a specific team.
-
E.
winningCaptain
Indicates that the subject is the captain of a team that has won a particular match, tournament, or competition.
- 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_69bd43d2f1c081908cd4b7ec48ecc73d |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd5a342ffc8190a911d0598ed230bb |
completed | March 20, 2026, 2:31 p.m. |
| PD | Predicate disambiguation | batch_69bd5233cb5081908807e2b150f0ca06 |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:13 p.m.