Triple
T33412217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uber Diamond |
E855617
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Uber rider loyalty tier |
C33483
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Uber rider loyalty tier Context triple: [Uber Diamond, instanceOf, Uber rider loyalty tier]
-
A.
airline loyalty tier
An airline loyalty tier is a classification level within a frequent-flyer program that grants travelers escalating benefits and privileges based on their accumulated travel activity or spending with the airline.
-
B.
driver rewards program
A driver rewards program is a system that incentivizes and recognizes drivers’ performance, safety, and loyalty through points, benefits, and exclusive offers.
-
C.
Loyalty program status level
chosen
A loyalty program status level represents a tiered membership state assigned to a customer based on their accumulated activity or value, determining the specific benefits, rewards, and privileges they receive.
-
D.
mobility services provider
A mobility services provider is an organization that offers and manages transportation solutions—such as ride-hailing, car-sharing, bike or scooter rentals, and integrated transit services—to enable people and goods to move efficiently from one place to another.
-
E.
frequent flyer status-earning metric
A frequent flyer status-earning metric is a quantified measure (such as miles, segments, or points) that tracks a traveler’s progress toward achieving or maintaining elite status in an airline loyalty program.
- F. None of above.
Provenance (1 batch)
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_69f3496f04a08190804e56ac5098b8e4 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:36 a.m.