Triple

T10269518
Position Surface form Disambiguated ID Type / Status
Subject United Global Services E240797 entity
Predicate loyaltyProgramFocus P93034 FINISHED
Object high-spend customers 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: high-spend customers | Statement: [United Global Services, loyaltyProgramFocus, high-spend customers]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: loyaltyProgramFocus
Context triple: [United Global Services, loyaltyProgramFocus, high-spend customers]
  • A. loyaltyProgramType
    Indicates the specific category or kind of loyalty program associated with an entity (such as points-based, tiered, or subscription-based).
  • B. loyaltyIncentive
    Indicates a relationship where benefits or rewards are provided to encourage or recognize continued commitment or repeat engagement.
  • C. loyaltyProgramAccess
    Indicates that an entity is granted rights or eligibility to participate in a specific loyalty or rewards program.
  • D. loyaltyCurrencyProgram
    Indicates a relationship where an entity participates in or is associated with a loyalty or rewards currency program that tracks and grants benefits based on activity or purchases.
  • E. loyaltyIntegration
    Indicates the degree to which a loyalty or rewards program is connected, synchronized, or functionally embedded with another system, platform, or service.
  • 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_69d381a94c1881908fc38fc263d9b9c2 completed April 6, 2026, 9:49 a.m.
NER Named-entity recognition batch_69d4d2872830819080fdfa816167d04c completed April 7, 2026, 9:46 a.m.
PD Predicate disambiguation batch_69d4d1ef6e6c81908a8ee52e4d28127b completed April 7, 2026, 9:44 a.m.
PDg Predicate description generation batch_69d4d285812c8190ab910dc85c53eebf completed April 7, 2026, 9:46 a.m.
Created at: April 6, 2026, 11:35 a.m.