Triple
T24319605
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alaska SkyWest |
E612921
|
entity |
| Predicate | frequentFlyerProgramUsed |
P13481
|
FINISHED |
| Object | 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: Mileage Plan | Statement: [Alaska SkyWest, frequentFlyerProgramUsed, Mileage Plan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frequentFlyerProgramUsed Context triple: [Alaska SkyWest, frequentFlyerProgramUsed, Mileage Plan]
-
A.
associatedWithFrequentFlyerProgram
chosen
Indicates that an entity has a connection or involvement with a frequent flyer program, such as membership, participation, or affiliation.
-
B.
isFlownWith
Indicates that one entity travels by air together with, or using the same flight as, another entity.
-
C.
usedForPassengerFlights
Indicates that something serves as a means or facility for transporting passengers on flights.
-
D.
isFlownOn
Indicates that an entity (such as a person or object) travels or is transported using a particular aircraft or airline as the means of flight.
-
E.
hasAwardProgram
Indicates that an entity maintains or offers a formal award or recognition program.
- 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_69e2d7da491c8190b6e6218af50923db |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f292aa63fc8190a874367c9010f283 |
completed | April 29, 2026, 11:22 p.m. |
| PD | Predicate disambiguation | batch_69f1c45f45888190a9ccc225906c34bd |
completed | April 29, 2026, 8:42 a.m. |
Created at: April 18, 2026, 1:48 a.m.