Triple
T10524494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Copa ConnectMiles Platinum |
E248261
|
entity |
| Predicate | statusCardBranding |
P94377
|
FINISHED |
| Object | Star Alliance Gold logo |
—
|
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: Star Alliance Gold logo | Statement: [Copa ConnectMiles Platinum, statusCardBranding, Star Alliance Gold logo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusCardBranding Context triple: [Copa ConnectMiles Platinum, statusCardBranding, Star Alliance Gold logo]
-
A.
brandingStatus
Indicates the current state or condition of an entity’s branding, such as whether its brand identity has been defined, applied, updated, or is pending.
-
B.
cardBrandPlacement
Indicates the specific position or context in which a card brand is displayed or presented.
-
C.
issuerBrandName
Indicates the brand name associated with the entity that issues a product, document, or instrument.
-
D.
issuerBrandPortfolioIncludes
Indicates that an issuer’s overall brand portfolio contains or encompasses a particular brand.
-
E.
cardBrandsInvolved
Indicates that specific payment card brands are involved or participate in a given transaction, process, or context.
- 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_69d381c5c7448190bec34bee7ec72bac |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d509f4020c8190b78c49da086df757 |
completed | April 7, 2026, 1:43 p.m. |
| PD | Predicate disambiguation | batch_69d4fb94fa10819091f585bab4379c6f |
completed | April 7, 2026, 12:41 p.m. |
| PDg | Predicate description generation | batch_69d4fe06d4a48190b1a45dd1d4e16df0 |
completed | April 7, 2026, 12:52 p.m. |
Created at: April 6, 2026, 12:29 p.m.