Triple
T29520103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Delano Las Vegas |
E748907
|
entity |
| Predicate | usesCasinoOf |
P66934
|
FINISHED |
| Object | Mandalay Bay |
—
|
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: Mandalay Bay | Statement: [Delano Las Vegas, usesCasinoOf, Mandalay Bay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesCasinoOf Context triple: [Delano Las Vegas, usesCasinoOf, Mandalay Bay]
-
A.
hasCasino
Indicates that an entity includes, contains, or is associated with a casino facility or gambling establishment.
-
B.
associatedWithCasino
chosen
Indicates a relationship where an entity has a connection or involvement with a casino, such as through ownership, operation, affiliation, or regular activity.
-
C.
hasCasinoWebsite
Indicates that an entity operates, is associated with, or is represented by a website specifically dedicated to casino-related activities or services.
-
D.
hasNearbyCasino
Indicates that one entity is located close to, or in the immediate vicinity of, a casino.
-
E.
casinoLocatedIn
Indicates that a casino is situated within or belongs to a specific geographic or administrative location.
- 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_69f0bd461c208190bec20bbf24e02cc5 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f7805ce6208190ac6dbd9c97989978 |
completed | May 3, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69f77956ec648190ba4fb7e9d83fd107 |
completed | May 3, 2026, 4:35 p.m. |
Created at: April 28, 2026, 4:40 p.m.