Triple
T31307751
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States to Latin America remittance corridor |
E798379
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | cross-border payment corridor |
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: cross-border payment corridor Context triple: [United States to Latin America remittance corridor, instanceOf, cross-border payment corridor]
-
A.
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.
-
B.
cross-border institution
A cross-border institution is an organization or entity that operates across national boundaries, coordinating policies, activities, or services between multiple countries or jurisdictions.
-
C.
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.
-
D.
cross-border terminal
A cross-border terminal is a transportation facility located at or near an international boundary that consolidates, processes, and transfers passengers or freight between different countries’ transport networks while handling customs, immigration, and regulatory controls.
-
E.
cross-border transport link
A cross-border transport link is an infrastructure connection—such as a road, railway, bridge, tunnel, or ferry route—that enables the movement of people and goods between two or more countries.
- 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.