Triple
T32387928
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | China Development Bank |
E827587
|
entity |
| Predicate | alsoOperatesInCurrency |
P4256
|
FINISHED |
| Object | US dollar |
—
|
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: US dollar | Statement: [China Development Bank, alsoOperatesInCurrency, US dollar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alsoOperatesInCurrency Context triple: [China Development Bank, alsoOperatesInCurrency, US dollar]
-
A.
usesCurrency
Indicates that one entity conducts its financial transactions or values using the monetary unit represented by the other entity.
-
B.
involvesCurrency
chosen
Indicates that the relationship or action includes or pertains to the use, exchange, or specification of a particular currency.
-
C.
servesCurrencyUnion
Indicates that an entity functions as the central authority or administrative body for a specific currency union.
-
D.
associatedCurrencyCode
Indicates the currency code that is linked to or used in connection with the given entity or transaction.
-
E.
currencyOnboard
Indicates that a particular currency has been enabled, registered, or made available for use within a given system or context.
- 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_69f349184e7481909c6c54428cb9cf12 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c1d325308190a1dc982b40203152 |
completed | May 3, 2026, 3:32 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6eb32c8190bf405b2011fa48f7 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:51 a.m.