Triple
T8362407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Delta SkyMiles Blue American Express Card |
E197039
|
entity |
| Predicate | doesNotIncludeBenefit |
P10124
|
FINISHED |
| Object | complimentary checked bag |
—
|
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 checked bag | Statement: [Delta SkyMiles Blue American Express Card, doesNotIncludeBenefit, complimentary checked bag]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: doesNotIncludeBenefit Context triple: [Delta SkyMiles Blue American Express Card, doesNotIncludeBenefit, complimentary checked bag]
-
A.
doesNotCover
chosen
Indicates that one entity fails to include, protect, or extend over another entity or area.
-
B.
hasBenefit
Indicates that one entity provides an advantage, improvement, or positive outcome to another entity.
-
C.
isIndividualBenefit
Indicates that something provides a benefit or advantage to a single individual rather than to a group or collective.
-
D.
hasBenefitType
Indicates that an entity is associated with a specific category or type of benefit it provides or receives.
-
E.
benefitProtection
Indicates that one entity provides protective advantages or safeguards that benefit 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_69ca82f2dbe48190aba982e75a0d94de |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb8074e4588190b394d1622adca2cb |
completed | March 31, 2026, 8:06 a.m. |
| PD | Predicate disambiguation | batch_69cb70ca25548190b0f90c5384e3fb3c |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 6 p.m.