Triple
T15023149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand Hotel Sopot |
E378135
|
entity |
| Predicate | isAccommodationType |
P53265
|
FINISHED |
| Object | seaside resort hotel |
—
|
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: seaside resort hotel | Statement: [Grand Hotel Sopot, isAccommodationType, seaside resort hotel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAccommodationType Context triple: [Grand Hotel Sopot, isAccommodationType, seaside resort hotel]
-
A.
hasAccommodation
Indicates that an entity provides, owns, or is associated with a place for someone to stay or live.
-
B.
hasHotelType
chosen
Indicates that a hotel is classified as belonging to a specific type or category (e.g., resort, boutique, hostel).
-
C.
hasLodgeType
Indicates that an entity is associated with or classified by a particular type or category of lodge.
-
D.
accommodationStyle
Indicates the manner or type of lodging or housing arrangement provided or used in a given context.
-
E.
sleepingAccommodation
Indicates that one entity serves as a place or facility where another entity can sleep or stay overnight.
- 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_69d85cd3a3c881908c71fc424d459c17 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded7de117c8190a1b9fa8d1602057e |
completed | April 15, 2026, 12:12 a.m. |
| PD | Predicate disambiguation | batch_69de9a67cbc481909c19c2de57de4eb7 |
completed | April 14, 2026, 7:50 p.m. |
Created at: April 10, 2026, 2:56 a.m.