Triple
T33484116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Westin Peachtree Plaza Hotel |
E857562
|
entity |
| Predicate | rooftopRestaurant |
P176666
|
FINISHED |
| Object | The Sun Dial Restaurant, Bar & View |
—
|
NE NERFINISHED |
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: The Sun Dial Restaurant, Bar & View | Statement: [Westin Peachtree Plaza Hotel, rooftopRestaurant, The Sun Dial Restaurant, Bar & View]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rooftopRestaurant Context triple: [Westin Peachtree Plaza Hotel, rooftopRestaurant, The Sun Dial Restaurant, Bar & View]
-
A.
hasRooftop
Indicates that one entity possesses or is equipped with a rooftop as a structural feature.
-
B.
hasViewFromRooftop
Indicates that an entity provides or features a view observable from its rooftop.
-
C.
restaurantDesignedBy
Indicates that a restaurant was created or planned by a particular designer or architect.
-
D.
hasRooftopSpace
Indicates that an entity includes or provides an accessible rooftop area intended for use or occupancy.
-
E.
hasRooftopStructure
Indicates that one entity possesses or features a structural element located on its roof.
- 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_69f3497547608190a1a0f2365fb713ee |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e531be388190b1b4a0cb1bc1da75 |
completed | May 3, 2026, 6:03 a.m. |
| PD | Predicate disambiguation | batch_69f6e3da41948190a4cfe866ce184f73 |
completed | May 3, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69f6e47c13348190a10528c84a401178 |
completed | May 3, 2026, 6 a.m. |
Created at: May 1, 2026, 1:38 a.m.