Triple

T6253426
Position Surface form Disambiguated ID Type / Status
Subject Chief Technology Officer of Stripe E140101 entity
Predicate employer P7 FINISHED
Object Stripe E135777 NE 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: Stripe | Statement: [Chief Technology Officer of Stripe, employer, Stripe]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Stripe
Context triple: [Chief Technology Officer of Stripe, employer, Stripe]
  • A. Stripe chosen
    Stripe is a leading financial technology company that provides online payment processing and related services for internet businesses worldwide.
  • B. Braintree Direct
    Braintree Direct is an online payment processing solution that enables businesses to securely accept and manage credit cards, digital wallets, and other payment methods through web and mobile applications.
  • C. WePay
    WePay is an online payment services company that provides integrated payment processing solutions for platforms, marketplaces, and software providers.
  • D. Chase Paymentech
    Chase Paymentech is a payment processing and merchant services provider specializing in credit card and electronic transaction solutions for businesses.
  • E. PayPal
    PayPal is a leading global online payment platform that enables individuals and businesses to send, receive, and manage digital payments securely over the internet.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69c008b4858c819095b0199114a9a87b completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c063625608819081f5422112c80ce5 completed March 22, 2026, 9:47 p.m.
NED1 Entity disambiguation (via context triple) batch_69c2442a556081908b91e7d999a82514 completed March 24, 2026, 7:58 a.m.
Created at: March 22, 2026, 4:24 p.m.