Triple

T9555962
Position Surface form Disambiguated ID Type / Status
Subject JetBlue Plus Card E230539 entity
Predicate lateFeeType P37869 FINISHED
Object late payment fee may apply per cardmember agreement — 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: late payment fee may apply per cardmember agreement | Statement: [JetBlue Plus Card, lateFeeType, late payment fee may apply per cardmember agreement]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: lateFeeType
Context triple: [JetBlue Plus Card, lateFeeType, late payment fee may apply per cardmember agreement]
  • A. feeType chosen
    Indicates the specific category or classification of a fee associated with a transaction, service, or obligation.
  • B. chargeType
    Indicates the category or nature of a charge applied in a transaction or interaction between entities (e.g., fee type, billing classification, or legal charge type).
  • C. fareType
    Indicates the category or class of fare (such as standard, discounted, or promotional) that applies to a given trip, ticket, or pricing instance.
  • D. feeTypeAuthorized
    Indicates that a particular type of fee is permitted or approved for use in a given context or relationship.
  • E. fareCollectionType
    Indicates the method or system used to collect fares or payments for a service.
  • 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_69ca847d3be8819099c9dad2a7e786f1 completed March 30, 2026, 2:11 p.m.
NER Named-entity recognition batch_69cd9927209c8190bbb494fc9003bc99 completed April 1, 2026, 10:16 p.m.
PD Predicate disambiguation batch_69ccd594d0ac8190a81bc11a3a538167 completed April 1, 2026, 8:21 a.m.
Created at: March 30, 2026, 8:03 p.m.