Triple
T7965482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leonardo AdvantageCLUB |
E185190
|
entity |
| Predicate | rewardMechanism |
P80047
|
FINISHED |
| Object | earn points on eligible stays |
—
|
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: earn points on eligible stays | Statement: [Leonardo AdvantageCLUB, rewardMechanism, earn points on eligible stays]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rewardMechanism Context triple: [Leonardo AdvantageCLUB, rewardMechanism, earn points on eligible stays]
-
A.
rewardModel
Indicates a relationship where one entity serves as a model or framework for assigning rewards or evaluating outcomes for another entity or process.
-
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.
rewardUse
Indicates that one entity grants or provides a reward in response to the use or utilization of another entity.
-
D.
rewardRedemption
Indicates the act of exchanging accumulated rewards, points, or benefits for goods, services, or other forms of value.
-
E.
rewardFulfilledFor
Indicates that a previously promised or expected reward has been delivered or satisfied for a particular entity.
- F. None of above. chosen
Provenance (4 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_69ca8297699481909b75a405f01e03af |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3ba262208190887169fe94e47b0e |
completed | March 31, 2026, 3:12 a.m. |
| PD | Predicate disambiguation | batch_69cb0473d7dc8190a25d0cf460b9fcbe |
completed | March 30, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69cb14bbbacc81909c6cf8ec35314bbb |
completed | March 31, 2026, 12:26 a.m. |
Created at: March 30, 2026, 5:12 p.m.