Triple
T31307752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States to Latin America remittance corridor |
E798379
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | international money transfer channel |
C57815
|
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: international money transfer channel Context triple: [United States to Latin America remittance corridor, instanceOf, international money transfer channel]
-
A.
money transfer service
A money transfer service is a system that securely moves funds from one party to another, often across different accounts, institutions, or geographic locations.
-
B.
remittance corridor
chosen
A remittance corridor is the specific cross-border payment channel between a sending country and a receiving country through which migrant workers’ money transfers regularly flow.
-
C.
international settlement
An international settlement is a financial arrangement or process through which cross-border payments and obligations between countries, institutions, or entities are cleared and finalized, often involving foreign exchange and international banking systems.
-
D.
cross-border investment channel
A cross-border investment channel is a structured mechanism or platform that enables the flow of capital between investors and assets located in different countries, while managing regulatory, currency, and operational complexities.
-
E.
payment channel network
A payment channel network is a layer-2 system of interconnected off-chain payment channels that allows participants to route fast, low-cost transactions across a network without recording each transfer on the underlying blockchain.
- F. None of above.
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_69f224e0bd4c8190aab9b29a73f7aa3c |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 9:14 p.m.