Triple
T13026433
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holland |
E326319
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | less-than-truckload carrier |
C32359
|
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: less-than-truckload carrier Context triple: [Holland, instanceOf, less-than-truckload carrier]
-
A.
container shipping company
A container shipping company is a business that transports standardized cargo containers across oceans and other waterways using a fleet of specialized vessels, managing logistics, routing, and port operations.
-
B.
shipping company role
A shipping company role represents a specific set of responsibilities and permissions assigned to an individual or system within a shipping organization, defining how they interact with shipments, logistics processes, and related data.
-
C.
common carrier railroad
A common carrier railroad is a rail transport company that offers freight and/or passenger services to the general public under legal obligation to serve all customers without discrimination, according to published rates and schedules.
-
D.
freight forwarding company
A freight forwarding company is a logistics intermediary that arranges and manages the transportation, documentation, and customs clearance of goods on behalf of shippers across domestic and international supply chains.
-
E.
air cargo division
The air cargo division is the organizational unit within an airline or logistics company responsible for managing, coordinating, and optimizing the transportation of freight and mail by air.
- 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_69d8076cc45c81908123123f43e69266 |
completed | April 9, 2026, 8:09 p.m. |
Created at: April 9, 2026, 8:53 p.m.