Triple
T21752407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NSRGY |
E536946
|
entity |
| Predicate | underlyingShareCurrency |
P12372
|
FINISHED |
| Object | Swiss franc |
—
|
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: Swiss franc | Statement: [NSRGY, underlyingShareCurrency, Swiss franc]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: underlyingShareCurrency Context triple: [NSRGY, underlyingShareCurrency, Swiss franc]
-
A.
underlyingAsset
Indicates that one asset serves as the fundamental reference or basis for the value, performance, or contractual terms of another financial instrument or derivative.
-
B.
associatedCurrencyCode
chosen
Indicates the currency code that is linked to or used in connection with the given entity or transaction.
-
C.
currencyType
Indicates the specific kind of monetary unit or currency associated with an entity or transaction.
-
D.
currencyOfIssuance
Indicates the currency in which a financial instrument, obligation, or value is originally issued or denominated.
-
E.
isDenominatedIn
Indicates that something (such as a price, value, or account) is expressed or measured in a particular currency or unit of denomination.
- 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_69e0c46eab808190b848242d63a17c47 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f01d8b8b9c8190b1f6a8bc25d69dbb |
completed | April 28, 2026, 2:38 a.m. |
| PD | Predicate disambiguation | batch_69e6969c16fc8190b5126c169317d85d |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:50 p.m.