Triple
T19359992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deluxe Resort Hotels |
E484250
|
entity |
| Predicate | experiencePositioning |
P135234
|
FINISHED |
| Object | luxury-focused Disney lodging option |
—
|
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: luxury-focused Disney lodging option | Statement: [Deluxe Resort Hotels, experiencePositioning, luxury-focused Disney lodging option]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: experiencePositioning Context triple: [Deluxe Resort Hotels, experiencePositioning, luxury-focused Disney lodging option]
-
A.
positioning
Indicates the spatial or contextual arrangement of one entity relative to another or within a given environment.
-
B.
designPositioning
Indicates the spatial or conceptual placement of a design element relative to other elements or a defined reference.
-
C.
positionUse
Indicates how a particular position or role is utilized or functionally applied within a given context.
-
D.
positionCoached
Indicates that one entity served as a coach for another entity in a specific position or role.
-
E.
positionOn
Indicates that one entity is located on top of or at a specific place along the surface or extent of another entity.
- 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_69d8e8d305088190ad13571532aa454c |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e6190b343c81909734ba776fd196dc |
completed | April 20, 2026, 12:16 p.m. |
| PD | Predicate disambiguation | batch_69e4dd13a8cc81909cd02668564c9f29 |
completed | April 19, 2026, 1:48 p.m. |
| PDg | Predicate description generation | batch_69e4dde92ff481909006b3f9e8d639d4 |
completed | April 19, 2026, 1:51 p.m. |
Created at: April 10, 2026, 1:34 p.m.