Triple
T3310241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Super Bowl IX |
E69552
|
entity |
| Predicate | thirdQuarterScore |
P30631
|
FINISHED |
| Object | 9–0 Pittsburgh Steelers |
—
|
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: 9–0 Pittsburgh Steelers | Statement: [Super Bowl IX, thirdQuarterScore, 9–0 Pittsburgh Steelers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: thirdQuarterScore Context triple: [Super Bowl IX, thirdQuarterScore, 9–0 Pittsburgh Steelers]
-
A.
scoringSummaryThirdQuarter
Indicates the summary of scoring events that occurred during the third quarter of a game.
-
B.
thirdQuarter
Indicates that something occurs in, belongs to, or is associated with the third quarter of a defined time period (such as a fiscal or calendar year).
-
C.
targetScoreAfterThreeQuarters
chosen
Indicates the score that a target entity has accumulated by the end of the third quarter of a game or timed event.
-
D.
thirdQuarterRepresents
Indicates that something serves as or corresponds to the third quarter portion of a whole (such as time, financial period, or sequence).
-
E.
quarterScores
Indicates the scores achieved in each quarter of a game, match, or period-based event.
- 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_69ad859f218081909458d2cebbf57565 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb0eb6dd08190bab1ce80f417966a |
completed | March 8, 2026, 5:24 p.m. |
| PD | Predicate disambiguation | batch_69ada4282730819092aa39c5f9269df0 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:11 p.m.