Triple
T6120599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CNH |
E136472
|
entity |
| Predicate | differenceFromCNY |
P68249
|
FINISHED |
| Object | traded outside mainland China's onshore market |
—
|
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: traded outside mainland China's onshore market | Statement: [CNH, differenceFromCNY, traded outside mainland China's onshore market]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: differenceFromCNY Context triple: [CNH, differenceFromCNY, traded outside mainland China's onshore market]
-
A.
conversionCostCurrency
Indicates the currency in which the cost of a conversion or transformation is denominated.
-
B.
valueInPhilippinePeso
Indicates the monetary value of something expressed in Philippine pesos as the unit of currency.
-
C.
valueInUSD
Indicates that a given amount or asset is expressed or evaluated in terms of its monetary value in United States dollars (USD).
-
D.
currencyProject
Indicates a relationship where a project is associated with, uses, or is denominated in a particular currency.
-
E.
currencyPlanned
Indicates that a specific currency is intended or scheduled to be used in a planned transaction, budget, or financial arrangement.
- F. None of above. chosen
Provenance (4 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_69c0089f851c81909e5e189a617dcff6 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c05bef8dc08190b917ad7209188c62 |
completed | March 22, 2026, 9:15 p.m. |
| PD | Predicate disambiguation | batch_69c049f9ab3c81909c8ab6466f6a2935 |
completed | March 22, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69c04e8e3f2c8190be459ca02f9b315a |
completed | March 22, 2026, 8:18 p.m. |
Created at: March 22, 2026, 4:14 p.m.