Triple
T4632384
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Super Bowl XXXIV |
E101445
|
entity |
| Predicate | quarterOfDecisivePlay |
P15369
|
FINISHED |
| Object | 4th quarter |
—
|
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: 4th quarter | Statement: [Super Bowl XXXIV, quarterOfDecisivePlay, 4th quarter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: quarterOfDecisivePlay Context triple: [Super Bowl XXXIV, quarterOfDecisivePlay, 4th quarter]
-
A.
decidingPlay
Indicates that an action or event serves as the critical play that determines the outcome of a game or contest.
-
B.
notablePlayQuarter
Indicates that a particular play or action in a game is considered especially significant or noteworthy within a specific quarter.
-
C.
fourthQuarter
chosen
Indicates that an event, action, or state occurs during the fourth quarter of a defined time period (such as a fiscal year or sports game).
-
D.
decisiveGamePitcher
Indicates that the pitcher played in the decisive game that determined the outcome of a series or championship.
-
E.
decidingMatchFor
Indicates a relationship where one entity is chosen or determined as the appropriate or final match for another entity among possible alternatives.
- 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.