Triple
T18825956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sunset Tower Hotel |
E460385
|
entity |
| Predicate | hasInteriorDesignStyle |
P5509
|
FINISHED |
| Object | Old Hollywood glamour |
—
|
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: Old Hollywood glamour | Statement: [Sunset Tower Hotel, hasInteriorDesignStyle, Old Hollywood glamour]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInteriorDesignStyle Context triple: [Sunset Tower Hotel, hasInteriorDesignStyle, Old Hollywood glamour]
-
A.
interiorStyle
chosen
Indicates that one entity has a particular interior design style or aesthetic characterized by the other entity.
-
B.
hasRichInteriorDecoration
Indicates that an entity features elaborate, ornate, or luxuriously detailed interior decoration.
-
C.
usesHouseStyle
Indicates that one entity follows or applies the specific house style (a defined set of stylistic or formatting conventions) associated with another entity.
-
D.
hasInteriorFeature
Indicates that an entity contains or includes a specific feature within its interior space.
-
E.
partOfInteriorDesign
Indicates that one entity is a component or element within the interior design scheme of another entity.
- 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_69d8dcf94c288190a06dea029ae4b223 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5a6bec7b08190b040ec8b3693f037 |
completed | April 20, 2026, 4:08 a.m. |
| PD | Predicate disambiguation | batch_69e48d1b10ec8190985c6fb5766ff981 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:56 a.m.