Triple
T33313087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Citi Premier Card |
E852939
|
entity |
| Predicate | pointsType |
P176475
|
FINISHED |
| Object | flexible transferable points |
—
|
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: flexible transferable points | Statement: [Citi Premier Card, pointsType, flexible transferable points]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pointsType Context triple: [Citi Premier Card, pointsType, flexible transferable points]
-
A.
points
Indicates that one entity directs attention, focus, or a physical/abstract indication toward another entity or location.
-
B.
pointDefinition
Indicates that one entity serves as the defining description or specification of a particular point in another entity.
-
C.
pointsSource
Indicates that one entity serves as the origin or source from which points (such as scores, credits, or coordinates) are derived or assigned to another entity.
-
D.
peakType
Indicates the specific classification or category of a peak based on its form, prominence, or other defining characteristics.
-
E.
typicalPositionType
Indicates the usual or most common positional role or placement type that an entity generally occupies or is associated with.
- 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_69f349679fd8819093b9b40e989440e3 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6e3156ea48190b604e414665ef351 |
completed | May 3, 2026, 5:54 a.m. |
| PD | Predicate disambiguation | batch_69f6de0b9ba48190887c9eb5d06a2e94 |
completed | May 3, 2026, 5:32 a.m. |
| PDg | Predicate description generation | batch_69f6e312d7fc819094dec41810f2585d |
completed | May 3, 2026, 5:54 a.m. |
Created at: May 1, 2026, 1:33 a.m.