Triple
T3310242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Super Bowl IX |
E69552
|
entity |
| Predicate | fourthQuarterScore |
P38580
|
FINISHED |
| Object | 16–6 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: 16–6 Pittsburgh Steelers | Statement: [Super Bowl IX, fourthQuarterScore, 16–6 Pittsburgh Steelers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fourthQuarterScore Context triple: [Super Bowl IX, fourthQuarterScore, 16–6 Pittsburgh Steelers]
-
A.
scoringSummaryFourthQuarter
chosen
Indicates the scoring events or point totals that occurred during the fourth quarter of a game.
-
B.
fourthQuarter
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).
-
C.
fourthQuarterRepresents
Indicates that something corresponds to, summarizes, or is used as the representation of the fourth quarter period (e.g., in time, performance, or reporting).
-
D.
quarterScores
Indicates the scores achieved in each quarter of a game, match, or period-based event.
-
E.
pointsNeededInFinalQuarter
Indicates the number of points a team or player must score in the final quarter to achieve a specific target or outcome.
- 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.