Triple
T7754511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OK Plus |
E175856
|
entity |
| Predicate | rewardCategory |
P1619
|
FINISHED |
| Object | air travel |
—
|
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: air travel | Statement: [OK Plus, rewardCategory, air travel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rewardCategory Context triple: [OK Plus, rewardCategory, air travel]
-
A.
rewardUse
Indicates that one entity grants or provides a reward in response to the use or utilization of another entity.
-
B.
rewardSignal
Indicates that one entity provides a signal representing feedback or incentive (such as a reward or penalty) to guide another entity’s behavior or learning process.
-
C.
awardSystem
Indicates a relationship where an entity establishes or uses a structured scheme for granting awards, honors, or recognitions to others.
-
D.
grantedAsRewardFor
Indicates that something is given to an entity specifically as a reward for a particular action, achievement, or service.
-
E.
awardType
chosen
Indicates the specific category or kind of award associated with an entity or event.
- 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_69c6996180088190832e38e8d83ff54a |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c705257ca08190a78c592a1e616da8 |
completed | March 27, 2026, 10:31 p.m. |
| PD | Predicate disambiguation | batch_69c7016df2b08190b2330a2010691431 |
completed | March 27, 2026, 10:15 p.m. |
Created at: March 27, 2026, 4:08 p.m.