Triple

T28052630
Position Surface form Disambiguated ID Type / Status
Subject Elevate E708867 entity
Predicate redemptionModel P163428 FINISHED
Object revenue-based pricing 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: revenue-based pricing | Statement: [Elevate, redemptionModel, revenue-based pricing]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: redemptionModel
Context triple: [Elevate, redemptionModel, revenue-based pricing]
  • A. redemptionType
    Indicates the manner or method by which something (such as a benefit, reward, or obligation) can be redeemed or fulfilled.
  • B. redemptionOptions
    Indicates the ways or methods by which something (such as points, credits, or vouchers) can be redeemed or exchanged for value.
  • C. redemptionCategory
    Indicates the classification or type under which something can be redeemed, such as how or for what it may be exchanged or claimed.
  • D. redeemedBy
    Indicates that something (such as a code, voucher, coupon, or offer) has been claimed, exchanged, or converted into its associated benefit or value by a particular entity.
  • E. redemptionDependsOn
    Indicates that the ability or process of redemption is contingent upon, or determined by, another specified factor or condition.
  • 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_69ef9b6df9f48190bbb971d02cbe1b65 completed April 27, 2026, 5:22 p.m.
NER Named-entity recognition batch_69f63fda178c8190b954cfab3cc26e22 completed May 2, 2026, 6:18 p.m.
PD Predicate disambiguation batch_69f637120c008190b2b5adf46f022e48 completed May 2, 2026, 5:40 p.m.
PDg Predicate description generation batch_69f637cad530819086cad3a5ec156013 completed May 2, 2026, 5:43 p.m.
Created at: April 27, 2026, 8:34 p.m.