Triple
T30964150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 0857.HK |
E788903
|
entity |
| Predicate | hasParValueCurrency |
P49198
|
FINISHED |
| Object | Renminbi |
—
|
NE NERFINISHED |
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: Renminbi | Statement: [0857.HK, hasParValueCurrency, Renminbi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParValueCurrency Context triple: [0857.HK, hasParValueCurrency, Renminbi]
-
A.
hasCurrencyProject
Indicates that an entity is associated with or involved in a specific currency-related project.
-
B.
hasSettlementCurrency
Indicates that a financial transaction, contract, or account is settled using a specified currency.
-
C.
associatedCurrencyCode
Indicates the currency code that is linked to or used in connection with the given entity or transaction.
-
D.
hasAssociatedCurrencyEntity
chosen
Indicates that an entity is linked to a specific currency entity that represents the monetary unit relevant to it.
-
E.
usesSupplementaryCurrency
Indicates that an entity employs an additional, non-primary currency alongside its main currency for transactions or value exchange.
- 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_69f224c3a6b48190951add9b7b7f0271 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe744faca881908e11e90e0a35653f |
completed | May 8, 2026, 11:39 p.m. |
| PD | Predicate disambiguation | batch_69fe734cbf7081909a552c5cf3b5ea59 |
completed | May 8, 2026, 11:35 p.m. |
Created at: April 29, 2026, 8:54 p.m.