Triple
T14374512
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 0992.HK |
E356438
|
entity |
| Predicate | hasReportingCurrencyOfIssuer |
P34487
|
FINISHED |
| Object | US dollar |
—
|
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: US dollar | Statement: [0992.HK, hasReportingCurrencyOfIssuer, US dollar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReportingCurrencyOfIssuer Context triple: [0992.HK, hasReportingCurrencyOfIssuer, US dollar]
-
A.
currencyOfIssuance
Indicates the currency in which a financial instrument, obligation, or value is originally issued or denominated.
-
B.
isDenominatedIn
chosen
Indicates that something (such as a price, value, or account) is expressed or measured in a particular currency or unit of denomination.
-
C.
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.
-
D.
hasISO4217Status
Indicates the classification or status of a currency according to the ISO 4217 standard.
-
E.
hasSettlementCurrency
Indicates that a financial transaction, contract, or account is settled using a specified currency.
- 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_69d8279163a081908aec45c0e3f1e02f |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de9007184c8190aebb003cb6548cc8 |
completed | April 14, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69de2a9cb3e081909f6b33fdd939bb9e |
completed | April 14, 2026, 11:53 a.m. |
Created at: April 10, 2026, 1:16 a.m.