Triple
T13278757
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AAdvantage |
E316261
|
entity |
| Predicate | eliteStatusMetric |
P12363
|
FINISHED |
| Object | Loyalty Points |
—
|
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: Loyalty Points | Statement: [AAdvantage, eliteStatusMetric, Loyalty Points]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eliteStatusMetric Context triple: [AAdvantage, eliteStatusMetric, Loyalty Points]
-
A.
eliteStatusProgram
Indicates a relationship where an entity is enrolled in or associated with a special high-tier or privileged status program.
-
B.
VIPStatus
Indicates that an entity holds a special or privileged status compared to others, often granting enhanced access, benefits, or priority treatment.
-
C.
statusQualificationMetric
chosen
Indicates a metric that qualifies, evaluates, or characterizes the status or condition of something in a measurable way.
-
D.
membershipLevelAbove
Indicates that one entity’s membership level is ranked higher or more privileged than another entity’s membership level.
-
E.
eliteField
Indicates that the entity is associated with a highly selective or top-tier field, domain, or area of specialization.
- 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_69d806b349908190a9a61dd9323bf153 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f6535688190a5a4549b7be2d611 |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:26 p.m.