Triple

T37538586
Position Surface form Disambiguated ID Type / Status
Subject Destiny 2 E933270 entity
Predicate originalMonetizationModel P94216 FINISHED
Object pay-to-play 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: pay-to-play | Statement: [Destiny 2, originalMonetizationModel, pay-to-play]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: originalMonetizationModel
Context triple: [Destiny 2, originalMonetizationModel, pay-to-play]
  • A. hasMonetizationFocus
    Indicates that one entity is oriented toward or primarily concerned with generating revenue or financial returns from another entity or activity.
  • B. supportsMonetizationProgram
    Indicates that an entity enables or is compatible with a specific monetization program, allowing revenue-generating activities to occur.
  • C. originalPriceModel
    Indicates the pricing relationship that specifies an item's initial or base price before any discounts, adjustments, or dynamic pricing are applied.
  • D. fundingModel
    Indicates how an entity is financially supported or sustained, such as through specific revenue sources, payment structures, or funding mechanisms.
  • E. usesRevenueModel chosen
    Indicates that one entity applies or operates according to a particular revenue model to generate income.
  • 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_69f76ec999288190ae26ec7b6aea7046 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_6a037c8efcd4819088c2aeead65d93df completed May 12, 2026, 7:16 p.m.
PD Predicate disambiguation batch_6a037a1553e08190bb7424c448cb1f33 completed May 12, 2026, 7:05 p.m.
Created at: May 3, 2026, 4:17 p.m.