Triple
T14643334
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HarBowl |
E343780
|
entity |
| Predicate | RavensSuperBowlRecordAfterGame |
P115191
|
FINISHED |
| Object | 2–0 |
—
|
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: 2–0 | Statement: [HarBowl, RavensSuperBowlRecordAfterGame, 2–0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: RavensSuperBowlRecordAfterGame Context triple: [HarBowl, RavensSuperBowlRecordAfterGame, 2–0]
-
A.
winningTeamSuperBowlTitlesAfterGame
Indicates the number of Super Bowl titles a team has won after a specific game has been played.
-
B.
RedskinsFranchiseSuperBowlLossesAfterGame
Indicates that the Washington Redskins franchise had a Super Bowl loss occurring after a specified game.
-
C.
PittsburghSuperBowlAppearancesAfterGame
Indicates the number of Super Bowl appearances the Pittsburgh team has made following a specified game.
-
D.
homeSuperBowlWin
Indicates that a team won the Super Bowl while playing in its home stadium or home city.
-
E.
RavensDefensiveTouchdowns
Indicates the number of touchdowns scored by the Ravens’ defense, typically by returning interceptions, fumbles, or blocked kicks for a score.
- F. None of above. chosen
Provenance (4 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_69d822e1a2cc81908e5bb93cf61ce3cc |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb4e80aa48190884bab800f357106 |
completed | April 14, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69de657359c88190b082e3e9f86fc1d7 |
completed | April 14, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69de716c17cc8190aeb85296abee85a7 |
completed | April 14, 2026, 4:55 p.m. |
Created at: April 10, 2026, 1:26 a.m.