Triple
T10988779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Value Resort Hotels |
E259701
|
entity |
| Predicate | designPriority |
P65476
|
FINISHED |
| Object | affordability over luxury amenities |
—
|
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: affordability over luxury amenities | Statement: [Value Resort Hotels, designPriority, affordability over luxury amenities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designPriority Context triple: [Value Resort Hotels, designPriority, affordability over luxury amenities]
-
A.
planningPriority
Indicates the relative importance or urgency assigned to an item, task, or objective when organizing or scheduling plans.
-
B.
designEmphasizes
chosen
Indicates that a design intentionally places special importance or focus on a particular feature, principle, or aspect over others.
-
C.
previousDesignFeature
Indicates that one design feature precedes another in a sequence or earlier version of a design.
-
D.
prioritises
Indicates that one entity gives greater importance, preference, or precedence to another entity or task over alternatives.
-
E.
designLead
Indicates that one entity serves as the primary designer or person in charge of leading the design work for another entity or project.
- 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_69d6aa8a6a548190a750f944ccdc8064 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d787b574d08190adec34b814a26437 |
completed | April 9, 2026, 11:04 a.m. |
| PD | Predicate disambiguation | batch_69d72e9055908190b438f039574aaaaf |
completed | April 9, 2026, 4:44 a.m. |
Created at: April 8, 2026, 9:24 p.m.