Triple
T8141921
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Global Upgrade Certificates |
E190116
|
entity |
| Predicate | incentivizes |
P79344
|
FINISHED |
| Object | loyalty to the issuing airline |
—
|
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: loyalty to the issuing airline | Statement: [Global Upgrade Certificates, incentivizes, loyalty to the issuing airline]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: incentivizes Context triple: [Global Upgrade Certificates, incentivizes, loyalty to the issuing airline]
-
A.
providesIncentivesTo
chosen
Indicates that one entity offers rewards, benefits, or motivations to another entity to encourage a desired behavior or outcome.
-
B.
encourages
Indicates actively motivating, supporting, or giving confidence to another entity to pursue an action, behavior, or state.
-
C.
inhibits
Indicates that one entity prevents, restrains, or reduces the activity, effect, or occurrence of another entity.
-
D.
ownerIncentive
Indicates that an owner has a motivation, benefit, or reward associated with a particular entity, action, or outcome.
-
E.
typeOfIncentive
Indicates the specific kind or category of incentive associated with an entity or action.
- 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_69ca82bd9900819099477cdc2eb4244f |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4443a3748190bbae79f1d673c03d |
completed | March 31, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69cb369c0d0481908762c488d7f77e74 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:36 p.m.