Triple
T12145528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Cosmopolitan of Las Vegas |
E289307
|
entity |
| Predicate | hasSportsbook |
P103208
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [The Cosmopolitan of Las Vegas, hasSportsbook, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSportsbook Context triple: [The Cosmopolitan of Las Vegas, hasSportsbook, yes]
-
A.
hasBookmakers
Indicates that an entity is associated with or utilizes one or more bookmakers for betting or odds-setting activities.
-
B.
hasSportsService
Indicates that an entity provides or is associated with a sports-related service.
-
C.
bettingOdds
Indicates the likelihood or probability of a particular outcome in a bet, typically expressed as numerical odds set for wagering.
-
D.
hasSportsStatus
Indicates that an entity holds a particular sports-related status, role, or classification (such as amateur, professional, active, or retired) within a sporting context.
-
E.
hasEsport
Indicates that an entity is associated with or participates in a specific electronic sports (esports) activity or competition.
- 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_69d6ab4c6710819097a9d228382dde43 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d915d7109481908bf5fe512bba3c89 |
completed | April 10, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69d9150c18148190bf8152189c0e5fca |
completed | April 10, 2026, 3:19 p.m. |
| PDg | Predicate description generation | batch_69d915d58ab881908b5b7901990308a4 |
completed | April 10, 2026, 3:23 p.m. |
Created at: April 8, 2026, 9:49 p.m.