Triple
T34660303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ken Jennings |
E890086
|
entity |
| Predicate | Jeopardy! regular-play winnings |
P179758
|
FINISHED |
| Object | $2,520,700 |
—
|
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,520,700 | Statement: [Ken Jennings, Jeopardy! regular-play winnings, $2,520,700]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Jeopardy! regular-play winnings Context triple: [Ken Jennings, Jeopardy! regular-play winnings, $2,520,700]
-
A.
Jeopardy! regular-play winning streak
Indicates the condition where a contestant has achieved consecutive wins during standard, non-tournament Jeopardy! games.
-
B.
hasWinnerInCategory Delight and Fun
Indicates that an entity has been recognized as a winner specifically in the "Delight and Fun" category.
-
C.
quizShowPrize
Indicates that one entity is the prize or reward awarded to another entity in the context of a quiz show.
-
D.
termNumberWon
Indicates the number of distinct terms or periods in which the subject has achieved a win or victory.
-
E.
JetsScore
Indicates that the team named Jets scores a certain number of points in a game or event.
- 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_69f349d906bc8190b2efd9eff237d94b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f727bde8f88190ad746ca515134ca1 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72739c30c81908642eef3feb3afcf |
completed | May 3, 2026, 10:45 a.m. |
| PDg | Predicate description generation | batch_69f727bd39b081908457590c3ba9b745 |
completed | May 3, 2026, 10:47 a.m. |
Created at: May 1, 2026, 2:04 a.m.