Triple
T5002250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mileage Plan |
E112400
|
entity |
| Predicate | loyaltyTier |
P35523
|
FINISHED |
| Object | Member |
—
|
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: Member | Statement: [Mileage Plan, loyaltyTier, Member]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: loyaltyTier Context triple: [Mileage Plan, loyaltyTier, Member]
-
A.
loyaltyProgramTierOf
chosen
Indicates the specific loyalty or rewards program tier that an entity (such as a customer or account) belongs to.
-
B.
loyaltyProgramType
Indicates the specific category or kind of loyalty program associated with an entity (such as points-based, tiered, or subscription-based).
-
C.
petitionerLoyaltyStatus
Indicates the current or historical loyalty or allegiance status of the petitioner in relation to a relevant authority, group, or cause.
-
D.
loyaltyDomain
Indicates a relationship where loyalty, allegiance, or steadfast support is directed toward or governed by a particular domain, context, or sphere of influence.
-
E.
loyaltyIntegration
Indicates the degree to which a loyalty or rewards program is connected, synchronized, or functionally embedded with another system, platform, or service.
- 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_69bd4433d0b08190877e83959ef40d81 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd7472a1dc8190942f568a81fdd961 |
completed | March 20, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69bd714aee2481908fb0dd5fa2daf3a1 |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:34 p.m.