Triple
T11586759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Majestic |
E274774
|
entity |
| Predicate | hasLuxuryStatus |
P68536
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [The Majestic, hasLuxuryStatus, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLuxuryStatus Context triple: [The Majestic, hasLuxuryStatus, true]
-
A.
isLuxuryHotel
chosen
Indicates that a hotel is classified as a luxury establishment, typically offering high-end amenities, services, and accommodations.
-
B.
hasVIPServices
Indicates that an entity provides or is associated with special or premium services reserved for very important persons (VIPs).
-
C.
hasLuxuryBrands
Indicates that an entity possesses, offers, or is associated with one or more luxury brands.
-
D.
hasLuxurySuites
Indicates that an entity provides or contains high-end, premium-quality suites as part of its accommodations or offerings.
-
E.
VIPStatus
Indicates that an entity holds a special or privileged status compared to others, often granting enhanced access, benefits, or priority treatment.
- 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_69d6aae6b14c81908dc5a74bad7591f9 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d89462203881908870e991a5b21770 |
completed | April 10, 2026, 6:10 a.m. |
| PD | Predicate disambiguation | batch_69d85dcbacd0819094d4a1237055affa |
completed | April 10, 2026, 2:17 a.m. |
Created at: April 8, 2026, 9:38 p.m.