Triple
T28052625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elevate |
E708867
|
entity |
| Predicate | pointsTransferDestination |
P57570
|
FINISHED |
| Object | Alaska Airlines Mileage Plan |
—
|
NE NERFINISHED |
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: Alaska Airlines Mileage Plan | Statement: [Elevate, pointsTransferDestination, Alaska Airlines Mileage Plan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pointsTransferDestination Context triple: [Elevate, pointsTransferDestination, Alaska Airlines Mileage Plan]
-
A.
transferDestination
chosen
Indicates the entity that serves as the receiving end or target location of a transfer from another entity.
-
B.
fundingDestination
Indicates the target entity or purpose to which financial resources are allocated or directed.
-
C.
transferBetween
Indicates a movement or handover of something from one entity to another, typically changing its location, ownership, or control between them.
-
D.
transferAfter
Indicates that one entity transfers something to another entity only after a specified event or condition has occurred.
-
E.
primaryUSDestination
Indicates that an entity’s main or most significant destination within the United States is the specified location.
- 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_69ef9b6df9f48190bbb971d02cbe1b65 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f6617ba4a88190bfc5c305acb4f93f |
completed | May 2, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f660f082508190a95a7888ad66cb2e |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 27, 2026, 8:34 p.m.