Triple
T9986675
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1922 Dixie Classic |
E196785
|
entity |
| Predicate | CentreRecordEnteringGame |
P91437
|
FINISHED |
| Object | 10–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: 10–0 | Statement: [1922 Dixie Classic, CentreRecordEnteringGame, 10–0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: CentreRecordEnteringGame Context triple: [1922 Dixie Classic, CentreRecordEnteringGame, 10–0]
-
A.
ramsRecordEnteringGame
Indicates the performance record (such as wins and losses) that the Rams team holds at the time they enter a particular game.
-
B.
KansasRecordEnteringGame
Indicates the statistical record or performance status that Kansas has at the moment a game begins.
-
C.
losingTeamRecordEnteringGame
Indicates that the team’s win-loss record prior to the game was a losing record (more losses than wins) entering that specific game.
-
D.
titansRecordEnteringGame
Indicates that the Titans team begins participation in a game, marking their official entry into the contest.
-
E.
BillsRecordEnteringGame
Indicates the statistical record or performance metrics that the Bills team has accumulated prior to the start of a particular game.
- 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_69ca82f1678c819093d06320a05f16a4 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdc79c8b80819091dc16ac8fd0c720 |
completed | April 2, 2026, 1:34 a.m. |
| PD | Predicate disambiguation | batch_69cd1da07db88190945bcdab3ca82e71 |
completed | April 1, 2026, 1:29 p.m. |
| PDg | Predicate description generation | batch_69cd358386f48190833c862b5b8c04b2 |
completed | April 1, 2026, 3:10 p.m. |
Created at: March 30, 2026, 8:49 p.m.