Triple
T5016789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apple One |
E112756
|
entity |
| Predicate | billingCurrency |
P245
|
FINISHED |
| Object | local currency by region |
—
|
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: local currency by region | Statement: [Apple One, billingCurrency, local currency by region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: billingCurrency Context triple: [Apple One, billingCurrency, local currency by region]
-
A.
currencyType
Indicates the specific kind of monetary unit or currency associated with an entity or transaction.
-
B.
currency
chosen
Indicates that one entity serves as the medium of exchange or monetary unit used by another entity (such as a country, region, or system).
-
C.
currencyDepicted
Indicates that one entity visually represents or shows the image or symbol of a particular currency on it.
-
D.
associatedCurrencyCode
Indicates the currency code that is linked to or used in connection with the given entity or transaction.
-
E.
usesCurrency
Indicates that one entity conducts its financial transactions or values using the monetary unit represented by the other entity.
- 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_69bd4434acb8819086679dbeccc2fe54 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd734037a88190a950db814412a023 |
completed | March 20, 2026, 4:18 p.m. |
| PD | Predicate disambiguation | batch_69bd714ecfe08190b5830cfc1c74fa17 |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:35 p.m.