Triple
T28249623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MQMs |
E712277
|
entity |
| Predicate | canBeGiftedVia |
P187033
|
FINISHED |
| Object | select Delta SkyMiles credit card benefits when allowed |
—
|
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: select Delta SkyMiles credit card benefits when allowed | Statement: [MQMs, canBeGiftedVia, select Delta SkyMiles credit card benefits when allowed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeGiftedVia Context triple: [MQMs, canBeGiftedVia, select Delta SkyMiles credit card benefits when allowed]
-
A.
giftability
Indicates the degree to which something is suitable or appropriate to be given as a gift.
-
B.
canGive
Indicates that one entity has the ability or permission to transfer something to another entity.
-
C.
canBeRedeemedFor
Indicates that one item, asset, or benefit may be exchanged or converted to obtain another specified item, asset, or benefit.
-
D.
giftedBy
Indicates that one entity has given or presented another entity as a gift to a recipient.
-
E.
canBePurchasedWith
Indicates that one entity is able to be bought or acquired using another entity as the form of payment.
- F. None of above. chosen
Provenance (4 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_69efb51fb98881909692421959ec0170 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69fb3425666081908916fcbf3b5dd907 |
completed | May 6, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69fb2f5f3164819099429c2cc3d24e01 |
completed | May 6, 2026, 12:09 p.m. |
| PDg | Predicate description generation | batch_69fb3424724c8190ba55ecf66fa0b171 |
completed | May 6, 2026, 12:29 p.m. |
Created at: April 27, 2026, 11:03 p.m.