Triple
T9555927
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JetBlue Plus Card |
E230539
|
entity |
| Predicate | earnsPointsCurrency |
P35525
|
FINISHED |
| Object | TrueBlue 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: TrueBlue points | Statement: [JetBlue Plus Card, earnsPointsCurrency, TrueBlue points]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earnsPointsCurrency Context triple: [JetBlue Plus Card, earnsPointsCurrency, TrueBlue points]
-
A.
earnsRewardsCurrency
chosen
Indicates that an entity receives or accumulates a specified rewards currency as a result of some action, status, or relationship.
-
B.
canBeEarnedBy
Indicates that something (such as a reward, status, or resource) is obtainable through the actions, efforts, or qualifications of a particular entity.
-
C.
currencyGiven
Indicates that one entity transfers or provides money or a monetary unit to another entity.
-
D.
pointsEarnedFrom
Indicates the number of points that an entity has received as a result of another specified source, action, or event.
-
E.
usesCurrency
Indicates that one entity conducts its financial transactions or values using the monetary unit represented by the other 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_69ca847d3be8819099c9dad2a7e786f1 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9927209c8190bbb494fc9003bc99 |
completed | April 1, 2026, 10:16 p.m. |
| PD | Predicate disambiguation | batch_69ccd594d0ac8190a81bc11a3a538167 |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:03 p.m.