Triple

T6894372
Position Surface form Disambiguated ID Type / Status
Subject GarudaMiles E159132 entity
Predicate loyaltyMechanism P73992 FINISHED
Object earn and burn miles 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 and burn miles | Statement: [GarudaMiles, loyaltyMechanism, earn and burn miles]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: loyaltyMechanism
Context triple: [GarudaMiles, loyaltyMechanism, earn and burn miles]
  • A. loyaltyIncentive
    Indicates a relationship where benefits or rewards are provided to encourage or recognize continued commitment or repeat engagement.
  • B. loyaltyIntegration
    Indicates the degree to which a loyalty or rewards program is connected, synchronized, or functionally embedded with another system, platform, or service.
  • C. loyaltySymbolizedBy
    Indicates that an instance of loyalty is represented or expressed by a particular symbol or emblem.
  • D. loyaltyProgramType
    Indicates the specific category or kind of loyalty program associated with an entity (such as points-based, tiered, or subscription-based).
  • E. loyaltyDomain
    Indicates a relationship where loyalty, allegiance, or steadfast support is directed toward or governed by a particular domain, context, or sphere of influence.
  • 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_69c6883568c8819081db6407e892cccc completed March 27, 2026, 1:37 p.m.
NER Named-entity recognition batch_69c6d931da24819096b9b205f2c0ebb0 completed March 27, 2026, 7:23 p.m.
PD Predicate disambiguation batch_69c6d7b7681481909ec50509b19fcf81 completed March 27, 2026, 7:17 p.m.
PDg Predicate description generation batch_69c6d8c48ba48190b8d3aa7b8d22816b completed March 27, 2026, 7:21 p.m.
Created at: March 27, 2026, 2:24 p.m.