Triple
T12678625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uniform Customs and Practice for Documentary Credits |
E302886
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | trade finance standard |
C31734
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: trade finance standard Context triple: [Uniform Customs and Practice for Documentary Credits, instanceOf, trade finance standard]
-
A.
finance book
A finance book is a written work that explains concepts, strategies, and practices related to managing money, investing, markets, and financial decision-making.
-
B.
trade law
Trade law is the body of rules and principles governing the exchange of goods, services, and capital across borders, including treaties, regulations, and dispute resolution mechanisms between nations and commercial entities.
-
C.
trade in services instrument
A trade in services instrument is a financial or contractual mechanism that facilitates, records, or manages cross-border transactions involving the provision of services rather than physical goods.
-
D.
financial settlement platform
A financial settlement platform is a system that facilitates the secure, accurate, and timely clearing and settlement of financial transactions between parties, often integrating payment processing, reconciliation, and reporting functions.
-
E.
financial messaging network
A financial messaging network is a secure, standardized communication infrastructure that enables financial institutions to exchange payment, settlement, and transaction-related messages reliably and efficiently.
- F. None of above. chosen
Provenance (1 batch)
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_69d7bdee64a08190801c6d470aefd723 |
completed | April 9, 2026, 2:55 p.m. |
Created at: April 9, 2026, 5:20 p.m.