Triple
T15597841
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LSU–Alabama football rivalry |
E374951
|
entity |
| Predicate | postseasonMeetingResult |
P79927
|
FINISHED |
| Object | Alabama win |
—
|
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: Alabama win | Statement: [LSU–Alabama football rivalry, postseasonMeetingResult, Alabama win]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postseasonMeetingResult Context triple: [LSU–Alabama football rivalry, postseasonMeetingResult, Alabama win]
-
A.
playoffResult
chosen
Indicates the outcome of a playoff contest or series between competitors, such as who advanced or was eliminated.
-
B.
postseasonSeries
Indicates that there is a multi-game playoff or postseason competition series taking place between entities (typically teams) within a sports or competitive context.
-
C.
postseasonType
Indicates the specific kind of postseason competition or phase associated with an event or team.
-
D.
postseasonSeriesWinner
Indicates which competitor or team won a particular postseason series in a sports or competitive context.
-
E.
postseasonEnd
Indicates the point in time or event at which a sports league’s postseason (playoffs) concludes.
- 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_69d85cce25008190b13b52745fbd719b |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04e609ab081909feb486a57439960 |
completed | April 16, 2026, 2:50 a.m. |
| PD | Predicate disambiguation | batch_69deda844af081909e658ebc9d9b403d |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:12 a.m.