Triple

T21922997
Position Surface form Disambiguated ID Type / Status
Subject Concierge (Aer Lingus AerClub tier) E541366 entity
Predicate customerRelationshipRole P99211 FINISHED
Object rewards loyal 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: rewards loyal customers | Statement: [Concierge (Aer Lingus AerClub tier), customerRelationshipRole, rewards loyal customers]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: customerRelationshipRole
Context triple: [Concierge (Aer Lingus AerClub tier), customerRelationshipRole, rewards loyal customers]
  • A. relationshipToCustomers chosen
    Indicates the type or nature of connection an entity has with its customers, such as role, status, or interaction pattern.
  • B. ClientRole
    Indicates that an entity participates in a relationship or interaction specifically in the capacity of a client.
  • C. salesRole
    Indicates that an entity holds a position or function related to selling products or services within a business context.
  • D. customerType
    Indicates the classification or category assigned to a customer based on their characteristics, status, or relationship with a business.
  • E. customerValue
    Indicates the degree of benefit, importance, or worth that a customer represents to a business or organization.
  • 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_69e0c47d74488190a15119108794a307 completed April 16, 2026, 11:14 a.m.
NER Named-entity recognition batch_69f1233d096c8190af0d7cd21879c91b completed April 28, 2026, 9:14 p.m.
PD Predicate disambiguation batch_69e6f5efc208819091ed2cf6841fa600 completed April 21, 2026, 3:58 a.m.
Created at: April 16, 2026, 7:45 p.m.