Triple
T38678550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1997 Rose Bowl |
E943823
|
entity |
| Predicate | homeTeamRecord |
P34055
|
FINISHED |
| Object | 10–1 |
—
|
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: 10–1 | Statement: [1997 Rose Bowl, homeTeamRecord, 10–1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeTeamRecord Context triple: [1997 Rose Bowl, homeTeamRecord, 10–1]
-
A.
homeTeamRecordEnteringGame
chosen
Indicates the win-loss (and possibly tie) record that the home team had prior to the start of the game.
-
B.
teamRecord
Indicates the recorded performance statistics (such as wins, losses, and ties) associated with a particular team over a defined period or competition.
-
C.
awayTeamRegularSeasonRecord
Indicates the win-loss (and possibly tie) record that the away team has accumulated during the regular season.
-
D.
homeTeam
Indicates that one entity is designated as the home team in a game, match, or sporting event involving another entity.
-
E.
seasonRecord
Indicates the overall performance or results an entity achieved over the course of a specific season (e.g., wins, losses, or comparable outcome metrics).
- 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_69f76eec28708190b9c82a505fc278e0 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fce545fec881909247a3af821d21ae |
completed | May 7, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69fce12eaeec81908cf81346b2cef6e0 |
completed | May 7, 2026, 6:59 p.m. |
Created at: May 3, 2026, 4:33 p.m.