Triple
T584480
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Super Bowl III |
E15128
|
entity |
| Predicate | favoritePointSpread |
P2628
|
FINISHED |
| Object | 18 |
—
|
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: 18 | Statement: [Super Bowl III, favoritePointSpread, 18]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: favoritePointSpread Context triple: [Super Bowl III, favoritePointSpread, 18]
-
A.
pointSpreadFavorite
chosen
Indicates which competitor or team is favored in a point spread betting line and by how many points they are expected to win.
-
B.
homeFieldAdvantage
Indicates that one participant benefits from playing or operating in a familiar or home environment, gaining an advantage over the opponent.
-
C.
favoriteTeam
Indicates that one entity is the sports team preferred above all others by another entity.
-
D.
usedInBettingLines
Indicates that something (such as data, statistics, or an event) is employed as a factor or component in determining betting lines or odds.
-
E.
winnerPoints
Indicates the number of points earned by the winning participant or entity in a competition or event.
- 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_69a4935783b8819082b77726ec10cc42 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49b9874c88190bd1e08d4689ea124 |
completed | March 1, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_69a494c9315c8190a773e8e00737d8a0 |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:33 p.m.