Triple
T34148754
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Park Las Vegas |
E875935
|
entity |
| Predicate | isBrandingElementOf |
P48662
|
FINISHED |
| Object | Park MGM resort area |
—
|
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: Park MGM resort area | Statement: [The Park Las Vegas, isBrandingElementOf, Park MGM resort area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isBrandingElementOf Context triple: [The Park Las Vegas, isBrandingElementOf, Park MGM resort area]
-
A.
hasBrandIdentityElement
chosen
Indicates that an entity includes or is associated with a specific component of its overall brand identity (such as a logo, color scheme, or tagline).
-
B.
hasBranding
Indicates that one entity carries, displays, or is associated with the brand identity of another entity.
-
C.
isBrand
Indicates that one entity functions as the commercial brand or label associated with another entity.
-
D.
hasParentBrandElement
Indicates that one brand-related element is hierarchically associated as a child or sub-component of another, which serves as its parent brand element.
-
E.
isPartOfBrandStrategy
Indicates that an action, element, or decision is included within and contributes to the overall brand strategy.
- 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_69f349abaa508190a820f206620efddc |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f70fb4f18c819099ef6d9177b7d205 |
completed | May 3, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69f70f3a54d481909ba6bdda3647b761 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:54 a.m.