Triple
T33413953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hyatt Regency Atlanta |
E855661
|
entity |
| Predicate | hasMeetingSpaceArea |
P15338
|
FINISHED |
| Object | large convention and meeting space |
—
|
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: large convention and meeting space | Statement: [Hyatt Regency Atlanta, hasMeetingSpaceArea, large convention and meeting space]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMeetingSpaceArea Context triple: [Hyatt Regency Atlanta, hasMeetingSpaceArea, large convention and meeting space]
-
A.
typeOfVenueArea
Indicates that a specific area or section is classified as a particular type of venue space (e.g., seating area, stage, lobby).
-
B.
hasConferenceSpace
chosen
Indicates that an entity provides or includes dedicated space suitable for holding conferences, meetings, or similar gatherings.
-
C.
hasFloorSpaceUse
Indicates how a given area of floor space is allocated or used for specific functions or activities.
-
D.
roomCapacity
Indicates the maximum number of people or occupants that a room is designed or allowed to hold.
-
E.
hasFloorArea
Indicates that an entity possesses a specified amount of floor space as a measurable area.
- 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_69fed48d8e148190a99c0aea29f8a3ee |
completed | May 9, 2026, 6:30 a.m. |
| PD | Predicate disambiguation | batch_69fed3c82a24819095e614e31ac0307f |
completed | May 9, 2026, 6:27 a.m. |
Created at: May 1, 2026, 1:36 a.m.