Triple
T6120589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CNH |
E136472
|
entity |
| Predicate | settlementCurrencyFor |
P12372
|
FINISHED |
| Object | international trade with China |
—
|
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: international trade with China | Statement: [CNH, settlementCurrencyFor, international trade with China]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: settlementCurrencyFor Context triple: [CNH, settlementCurrencyFor, international trade with China]
-
A.
settlementType
Indicates the specific kind or category of human settlement an entity represents, such as a city, village, town, or hamlet.
-
B.
typeOfSettlement
Indicates the specific category or classification of a settlement (e.g., city, town, village) that characterizes what kind of settlement it is.
-
C.
associatedCurrencyCode
chosen
Indicates the currency code that is linked to or used in connection with the given entity or transaction.
-
D.
currencyType
Indicates the specific kind of monetary unit or currency associated with an entity or transaction.
-
E.
currencyCodeDenoted
Indicates that a specific currency code is used to denote or represent a particular 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_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. |
Created at: March 22, 2026, 4:14 p.m.