Triple
T20465318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emirates First Class Lounge |
E502032
|
entity |
| Predicate | offersBeverageType |
P70752
|
FINISHED |
| Object | premium wines |
—
|
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: premium wines | Statement: [Emirates First Class Lounge, offersBeverageType, premium wines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offersBeverageType Context triple: [Emirates First Class Lounge, offersBeverageType, premium wines]
-
A.
hasBeverageCategory
chosen
Indicates that an entity is associated with or classified under a particular beverage category.
-
B.
offersFoodAndBeverage
Indicates that an entity provides both food and drink to another entity or for general consumption.
-
C.
offersServiceType
Indicates that one entity provides or makes available a specific type or category of service to another entity or the public.
-
D.
offersCuisine
Indicates that one entity provides or serves a particular type or style of cuisine to others.
-
E.
beverageSubcategory
Indicates a more specific classification within a broader beverage category, defining the subtype or subcategory of a drink.
- 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_69e0b4ae5f1081908768b0c9a3a0bf38 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e696a9489081908990c691a36ba04d |
completed | April 20, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69e57679eb40819086142df3e39c928e |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:33 a.m.