Triple
T8453301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CAR |
E199852
|
entity |
| Predicate | usedOnBettingBoards |
P8419
|
FINISHED |
| Object | sportsbooks |
—
|
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: sportsbooks | Statement: [CAR, usedOnBettingBoards, sportsbooks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedOnBettingBoards Context triple: [CAR, usedOnBettingBoards, sportsbooks]
-
A.
usedInBettingLines
chosen
Indicates that something (such as data, statistics, or an event) is employed as a factor or component in determining betting lines or odds.
-
B.
usedInFantasySportsPlatforms
Indicates that something (such as data, content, or a feature) is utilized within fantasy sports platforms for gameplay, management, or related functionality.
-
C.
betting
Indicates engaging in a wager where one party risks something of value on the outcome of an uncertain event involving another entity.
-
D.
usedInSport
Indicates that something (such as an object, technique, or concept) is employed or utilized within the context of a particular sport.
-
E.
isUsedToPlay
Indicates that something serves as an instrument, tool, or medium for engaging in a game, sport, or other form of play.
- 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_69ca8318231881908fd1bc1c4d45d286 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe48aee388190864ef1186d5ee419 |
completed | March 31, 2026, 3:13 p.m. |
| PD | Predicate disambiguation | batch_69cbd0fc634481909842c0a30077bfde |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:09 p.m.