Triple
T34877308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trade Corridor Enhancement Program |
E1005913
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | freight transportation program |
C26788
|
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: freight transportation program Context triple: [Trade Corridor Enhancement Program, instanceOf, freight transportation program]
-
A.
United States freight program
chosen
A United States freight program is a coordinated set of policies, investments, and initiatives designed to improve the efficiency, safety, capacity, and environmental performance of the nation’s freight transportation system across modes such as trucking, rail, maritime, and air cargo.
-
B.
freight transport sector
The freight transport sector encompasses the systems, services, and infrastructure involved in moving goods by road, rail, sea, air, and inland waterways across local, regional, and global supply chains.
-
C.
freight transport division
The freight transport division is the organizational unit responsible for planning, managing, and executing the movement of goods and cargo across various transportation modes within a company or network.
-
D.
freight brokerage
A freight brokerage is a business that connects shippers needing to move goods with carriers that have available transportation capacity, coordinating logistics and negotiating rates for both parties.
-
E.
freight carrier
A freight carrier is an entity (such as a company, vehicle, or vessel) responsible for transporting goods or cargo from one location to another, typically for commercial purposes.
- 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_69f76dbde1c08190a24e7f9beb564c8d |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4 p.m.