Triple
T10413792
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thai Royal Orchid Plus Gold |
E245461
|
entity |
| Predicate | loungeAccessScope |
P42519
|
FINISHED |
| Object | Star Alliance member airline lounges |
—
|
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: Star Alliance member airline lounges | Statement: [Thai Royal Orchid Plus Gold, loungeAccessScope, Star Alliance member airline lounges]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: loungeAccessScope Context triple: [Thai Royal Orchid Plus Gold, loungeAccessScope, Star Alliance member airline lounges]
-
A.
hasLoungeType
Indicates that an entity is associated with, or classified by, a particular type or category of lounge.
-
B.
accessScope
chosen
Indicates the extent or boundaries of access that one entity has to another entity or resource.
-
C.
hasAmenityAccessTo
Indicates that an entity has the right or ability to use or benefit from a specified amenity or facility.
-
D.
audienceAccess
Indicates that one entity has permission or ability to access, view, or engage with a particular audience associated with another entity.
-
E.
hasCustomerLounge
Indicates that an entity provides or includes a designated lounge area for customers to use.
- 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_69d381be340c8190b05998703d42d224 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4ea0ec6fc8190a71af759226a3cba |
completed | April 7, 2026, 11:27 a.m. |
| PD | Predicate disambiguation | batch_69d4dfb6f160819090040644a12395ec |
completed | April 7, 2026, 10:43 a.m. |
Created at: April 6, 2026, 12:10 p.m.