Triple
T32265769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chase Sapphire Preferred Card |
E824277
|
entity |
| Predicate | companionProduct |
P116472
|
FINISHED |
| Object | Chase Sapphire Reserve |
—
|
NE NERFINISHED |
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: Chase Sapphire Reserve | Statement: [Chase Sapphire Preferred Card, companionProduct, Chase Sapphire Reserve]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: companionProduct Context triple: [Chase Sapphire Preferred Card, companionProduct, Chase Sapphire Reserve]
-
A.
relatedToProduct
Indicates a general association or connection between an entity and a specific product, without specifying the exact nature of that relationship.
-
B.
providedProduct
Indicates that one entity has supplied or made available a particular product to another entity.
-
C.
includesCompanion
chosen
Indicates that one entity involves, contains, or is accompanied by another entity acting as a companion.
-
D.
concurrentProductWith
Indicates that two or more products are available, used, or occur at the same time within the same context or transaction.
-
E.
productWith
Indicates a relationship where one entity is associated with, contains, or is offered together with another entity as a product.
- 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_69f3490e73588190915f282edd105772 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fbbc49da8c8190902bbb05d2477cab |
completed | May 6, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69fbb13f34b08190bbbb220ac1e6e666 |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 1, 2026, 12:42 a.m.