Triple
T10413636
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Singapore Airlines PPS Club |
E245457
|
entity |
| Predicate | associatedStatusCurrency |
P75163
|
FINISHED |
| Object | PPS Value |
—
|
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: PPS Value | Statement: [Singapore Airlines PPS Club, associatedStatusCurrency, PPS Value]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedStatusCurrency Context triple: [Singapore Airlines PPS Club, associatedStatusCurrency, PPS Value]
-
A.
associatedCurrencyCode
Indicates the currency code that is linked to or used in connection with the given entity or transaction.
-
B.
statusCurrency
chosen
Indicates that a particular status or state is expressed, measured, or denominated in a specific currency.
-
C.
currencyCodeStatus
Indicates the current validity or operational state of a specified currency code within a given system or context.
-
D.
hasISO4217Status
Indicates the classification or status of a currency according to the ISO 4217 standard.
-
E.
currencyOnboard
Indicates that a particular currency has been enabled, registered, or made available for use within a given system or context.
- 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_69d381be340c8190b05998703d42d224 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4ea0ec6fc8190a71af759226a3cba |
completed | April 7, 2026, 11:27 a.m. |
| PD | Predicate disambiguation | batch_69d4dfb6f160819090040644a12395ec |
completed | April 7, 2026, 10:43 a.m. |
Created at: April 6, 2026, 12:10 p.m.