Triple

T23010605
Position Surface form Disambiguated ID Type / Status
Subject RY E572893 entity
Predicate isSubjectToCurrencyRiskForUSInvestors P94007 FINISHED
Object true 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: true | Statement: [RY, isSubjectToCurrencyRiskForUSInvestors, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isSubjectToCurrencyRiskForUSInvestors
Context triple: [RY, isSubjectToCurrencyRiskForUSInvestors, true]
  • A. currencyRisk chosen
    Indicates the exposure an entity has to potential financial loss or gain due to fluctuations in foreign exchange rates between currencies.
  • B. involvesCurrency
    Indicates that the relationship or action includes or pertains to the use, exchange, or specification of a particular currency.
  • C. hasInflationRisk
    Indicates that something is subject to potential loss of value or purchasing power due to inflation.
  • D. isWorldTradeCurrency
    Indicates that a currency is officially used and widely accepted as a medium of exchange in international trade and global financial transactions.
  • E. hasDominantCurrency
    Indicates that one currency is the primary or controlling medium of exchange or valuation within a given context, such as a market, region, or financial system.
  • 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_69e245b764cc8190a51be76f1d9611e1 completed April 17, 2026, 2:37 p.m.
NER Named-entity recognition batch_69f1835b0cb881908d3d2dd40cffcbc2 completed April 29, 2026, 4:04 a.m.
PD Predicate disambiguation batch_69ef3b9cd5488190bcd23183179f48cd completed April 27, 2026, 10:34 a.m.
Created at: April 17, 2026, 3:51 p.m.