Triple

T78351
Position Surface form Disambiguated ID Type / Status
Subject Coinstar E1568 entity
Predicate businessModelAspect P59 FINISHED
Object revenue from transaction fees 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 from transaction fees | Statement: [Coinstar, businessModelAspect, revenue from transaction fees]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: businessModelAspect
Context triple: [Coinstar, businessModelAspect, revenue from transaction fees]
  • A. economicAspect
    Indicates that something is related to, characterized by, or has implications for economic factors, conditions, or outcomes.
  • B. fundingModel chosen
    Indicates how an entity is financially supported or sustained, such as through specific revenue sources, payment structures, or funding mechanisms.
  • C. publishingModel
    Indicates the method or framework by which content is produced, distributed, and made publicly available.
  • D. operatesBy
    Indicates that an entity performs its function, action, or process through the use or application of another entity (e.g., a method, mechanism, or principle).
  • E. governanceModel
    Indicates the type or structure of authority, decision-making, and control that defines how an entity is directed and overseen.
  • 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_69a24c60d19c8190a1b6c105ca59ef5b completed Feb. 28, 2026, 2:01 a.m.
NER Named-entity recognition batch_69a2559892dc81909303f2eefdc0025f completed Feb. 28, 2026, 2:40 a.m.
PD Predicate disambiguation batch_69a24eaf99e481908e8d314577e22ecf completed Feb. 28, 2026, 2:10 a.m.
Created at: Feb. 28, 2026, 2:06 a.m.