Triple
T5595483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hotel Riu Plaza España |
E146986
|
entity |
| Predicate | cateringType |
P9631
|
FINISHED |
| Object | bed and breakfast available |
—
|
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: bed and breakfast available | Statement: [Hotel Riu Plaza España, cateringType, bed and breakfast available]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cateringType Context triple: [Hotel Riu Plaza España, cateringType, bed and breakfast available]
-
A.
cateringIncludes
Indicates that a catering service or arrangement encompasses or provides the specified item, service, or component as part of its offering.
-
B.
feastType
Indicates the specific kind or category of feast associated with an event or occasion.
-
C.
servesType
Indicates that one entity provides, offers, or is used to deliver a particular type, category, or kind of thing or service.
-
D.
servingOccasion
Indicates the occasion, event, or context during which something (typically food or drink) is served.
-
E.
diningStyle
chosen
Indicates the manner or format in which dining is conducted, such as casual, formal, buffet, or family-style.
- 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_69c009043d648190a7af89698ccf1e3e |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c020be029881908c5586838382c8f2 |
completed | March 22, 2026, 5:02 p.m. |
| PD | Predicate disambiguation | batch_69c01b1890ec8190b9e6fa488792e4d4 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:38 p.m.