Triple
T7153125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Executive Club |
E166741
|
entity |
| Predicate | statusCurrency |
P75163
|
FINISHED |
| Object | Tier 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: Tier Points | Statement: [Executive Club, statusCurrency, Tier Points]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusCurrency Context triple: [Executive Club, statusCurrency, Tier Points]
-
A.
currencyCodeStatus
Indicates the current validity or operational state of a specified currency code within a given system or context.
-
B.
currencyType
Indicates the specific kind of monetary unit or currency associated with an entity or transaction.
-
C.
currency
Indicates that one entity serves as the medium of exchange or monetary unit used by another entity (such as a country, region, or system).
-
D.
currencyContext
Indicates that a particular monetary value or transaction is expressed, interpreted, or valid within a specified currency framework or setting.
-
E.
denominationStatus
Indicates the current recognition, validity, or standing of a particular denomination within a specified system 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_69c68886779c8190a8e3fbabffe68253 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e7f52c1081908c4fa424d5e965bc |
completed | March 27, 2026, 8:26 p.m. |
| PD | Predicate disambiguation | batch_69c6e1caf4e48190b47bb398a3c1554d |
completed | March 27, 2026, 8 p.m. |
| PDg | Predicate description generation | batch_69c6e4a213508190a40aca39f9eee7d5 |
completed | March 27, 2026, 8:12 p.m. |
Created at: March 27, 2026, 2:46 p.m.