Triple
T36834681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Entertainment City |
E910237
|
entity |
| Predicate | firstIntegratedResortOpened |
P205076
|
FINISHED |
| Object | Solaire Resort & Casino |
E910242
|
NE 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: Solaire Resort & Casino | Statement: [Entertainment City, firstIntegratedResortOpened, Solaire Resort & Casino]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstIntegratedResortOpened Context triple: [Entertainment City, firstIntegratedResortOpened, Solaire Resort & Casino]
-
A.
secondIntegratedResortOpened
Indicates that the entity is the second integrated resort to have opened in a given context or location.
-
B.
casinoOpeningDate
Indicates the calendar date on which a casino first began operating or officially opened to the public.
-
C.
casinosBegan
Indicates that the activity, operation, or presence of casinos started at a particular time or in a particular context.
-
D.
originalAttractionOpeningDate
Indicates the date on which the attraction first opened to the public in its original form or location.
-
E.
firstLocationOpeningDate
Indicates the date on which the first location associated with the subject entity was opened.
- F. None of above. chosen
Provenance (5 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_69f76e7e9d60819092442fba73290a46 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3e2c203c088190b17e8dde3784ea2f |
completed | June 26, 2026, 7:37 a.m. |
| PD | Predicate disambiguation | batch_6a037a0e039481908a4a2666f76c5363 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82f8c88190bd77a086023ac0e1 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:13 p.m.