Triple
T22855737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Revel |
E566473
|
entity |
| Predicate | gamblingMarket |
P149994
|
FINISHED |
| Object | Atlantic City casino market |
—
|
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: Atlantic City casino market | Statement: [Revel, gamblingMarket, Atlantic City casino market]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gamblingMarket Context triple: [Revel, gamblingMarket, Atlantic City casino market]
-
A.
sportsMarketFor
Indicates a market or commercial context in which a particular sport, sporting event, or sports-related product is bought, sold, traded, or otherwise economically transacted.
-
B.
betting
Indicates engaging in a wager where one party risks something of value on the outcome of an uncertain event involving another entity.
-
C.
bettingOdds
Indicates the likelihood or probability of a particular outcome in a bet, typically expressed as numerical odds set for wagering.
-
D.
wageringAvailable
Indicates that it is possible to place bets or wagers on the associated event or entity.
-
E.
typeOfGambling
Indicates the specific category or form of gambling activity associated with an entity.
- 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_69e2458750b481908a8e4cf4609cc6cf |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17ebc6a088190890f2474f18a10eb |
completed | April 29, 2026, 3:45 a.m. |
| PD | Predicate disambiguation | batch_69eed2d507c08190895ed971af0fc755 |
completed | April 27, 2026, 3:07 a.m. |
| PDg | Predicate description generation | batch_69eeeb577e2081909f4a4e9c296535c0 |
completed | April 27, 2026, 4:51 a.m. |
Created at: April 17, 2026, 3:37 p.m.