Triple
T14743758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qatar Airways Privilege Club |
E346413
|
entity |
| Predicate | hasCoBrandedCreditCardsIn |
P115048
|
FINISHED |
| Object | selected markets |
—
|
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: selected markets | Statement: [Qatar Airways Privilege Club, hasCoBrandedCreditCardsIn, selected markets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoBrandedCreditCardsIn Context triple: [Qatar Airways Privilege Club, hasCoBrandedCreditCardsIn, selected markets]
-
A.
hadCoBrandedCreditCardsWith
chosen
Indicates that two entities jointly issued or partnered on one or more co-branded credit card products.
-
B.
cardBrandsInvolved
Indicates that specific payment card brands are involved or participate in a given transaction, process, or context.
-
C.
issuerBrandPortfolioIncludes
Indicates that an issuer’s overall brand portfolio contains or encompasses a particular brand.
-
D.
cardEligibility
Indicates whether an entity qualifies for or is allowed to receive a particular card under specified criteria.
-
E.
hasCredit
Indicates that an entity possesses or is assigned a credit, such as financial credit, academic credit, or acknowledgment for a contribution.
- 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_69d822e6f1c88190bc494d491a907114 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec7367a1c819081082cc355e385fa |
completed | April 14, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69de8bf9331481909582045cd567d91f |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:30 a.m.