Triple
T31655855
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Slap Bet |
E807856
|
entity |
| Predicate | slapBetCommissionerInEpisode |
P172070
|
FINISHED |
| Object | Lily Aldrin |
—
|
NE NERFINISHED |
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: Lily Aldrin | Statement: [Slap Bet, slapBetCommissionerInEpisode, Lily Aldrin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: slapBetCommissionerInEpisode Context triple: [Slap Bet, slapBetCommissionerInEpisode, Lily Aldrin]
-
A.
wagerGoal
Indicates that an entity sets or specifies a target outcome or objective for a wager or bet.
-
B.
bettingStructure
Indicates the rules and format governing how bets are placed, sized, and progressed within a wagering or game context.
-
C.
hasBettingStructure
Indicates that there is a specific set of rules or format governing how bets are placed and progressed in a game or wagering context.
-
D.
hasOutsideBet
Indicates that an entity has placed or holds a bet on an outcome considered an outside or less likely option in a given betting context.
-
E.
stakesType
Indicates the type or category of stakes involved in a given relationship, action, or situation.
- 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_69f348daf95c81908b4c985b7ddcd0b3 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a95e38ac819096c03f2b9872260f |
completed | May 3, 2026, 1:48 a.m. |
| PD | Predicate disambiguation | batch_69f6a757c6e081908e37631e5d8d246b |
completed | May 3, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f6a8036ab481908019f2f071fa406e |
completed | May 3, 2026, 1:42 a.m. |
Created at: April 30, 2026, 10:55 p.m.