Triple
T33413966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hyatt Regency Atlanta |
E855661
|
entity |
| Predicate | hasNotableDesignElement |
P198928
|
FINISHED |
| Object | multi-level open lobby |
—
|
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: multi-level open lobby | Statement: [Hyatt Regency Atlanta, hasNotableDesignElement, multi-level open lobby]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableDesignElement Context triple: [Hyatt Regency Atlanta, hasNotableDesignElement, multi-level open lobby]
-
A.
hasDesign
Indicates that one entity possesses, embodies, or is characterized by a particular design associated with another entity.
-
B.
hasDesignSignificance
Indicates that something possesses notable importance, impact, or relevance specifically in terms of its design.
-
C.
hasDesignCue
chosen
Indicates that one entity incorporates or features a specific design element, signal, or stylistic cue associated with another entity.
-
D.
hasNotableFeature
Indicates that an entity possesses a specific characteristic, trait, or attribute that is considered significant or noteworthy.
-
E.
hasDesignSide
Indicates that one entity is located on, associated with, or corresponds to a particular side or face of another entity’s design.
- 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_69f3496f04a08190804e56ac5098b8e4 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a01b935e3948190a7af37b07938d618 |
completed | May 11, 2026, 11:10 a.m. |
| PD | Predicate disambiguation | batch_6a01b8d198b48190b01e16ac9ce7e7bd |
completed | May 11, 2026, 11:09 a.m. |
Created at: May 1, 2026, 1:36 a.m.