Triple
T9855573
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | American Express Global Lounge Collection |
E239575
|
entity |
| Predicate | includesAmenity |
P79291
|
FINISHED |
| Object | complimentary Wi‑Fi |
—
|
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: complimentary Wi‑Fi | Statement: [American Express Global Lounge Collection, includesAmenity, complimentary Wi‑Fi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesAmenity Context triple: [American Express Global Lounge Collection, includesAmenity, complimentary Wi‑Fi]
-
A.
amenitiesInclude
chosen
Indicates that a place or facility provides or contains specific amenities as part of its features.
-
B.
hasAmenityAccessTo
Indicates that an entity has the right or ability to use or benefit from a specified amenity or facility.
-
C.
hasAccommodation
Indicates that an entity provides, owns, or is associated with a place for someone to stay or live.
-
D.
hasCivicAmenity
Indicates that an entity possesses, provides, or is associated with a public facility or service intended for community use.
-
E.
amenity
Indicates that one entity provides a useful facility, service, or feature that enhances the convenience or comfort of another entity.
- 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_69ca84e6493081909cf58c8d42ea856b |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb39719288190adf45e7c029edd51 |
completed | April 2, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69cd03e73ec48190bc30fa781978d817 |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:35 p.m.