Triple
T22855782
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Revel Atlantic City |
E566474
|
entity |
| Predicate | designedToAttract |
P59531
|
FINISHED |
| Object | upscale clientele |
—
|
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: upscale clientele | Statement: [Revel Atlantic City, designedToAttract, upscale clientele]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedToAttract Context triple: [Revel Atlantic City, designedToAttract, upscale clientele]
-
A.
attracts
Indicates that one entity exerts a force or influence that draws another entity toward it.
-
B.
designedToEvoke
Indicates that something was intentionally created or arranged in order to elicit a particular reaction, feeling, or response from an audience or observer.
-
C.
attractsAudience
chosen
Indicates that an entity draws the interest or attention of people who choose to watch, listen to, or engage with it.
-
D.
aimedAtBy
Indicates that one entity serves as the target or goal toward which another entity directs an action, intention, or focus.
-
E.
designedToCapture
Indicates that one entity was intentionally created or configured for the purpose of recording, containing, or acquiring another entity or a specific type of target.
- 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_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. |
Created at: April 17, 2026, 3:37 p.m.