Triple
T12153787
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indiana Harbor |
E289523
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | industrial port district |
C12386
|
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: industrial port district Context triple: [Indiana Harbor, instanceOf, industrial port district]
-
A.
industrial district
An industrial district is a designated urban or regional area characterized by a high concentration of manufacturing, warehousing, and related industrial activities supported by specialized infrastructure and services.
-
B.
coastal industrial area
A coastal industrial area is a shoreline zone dominated by factories, ports, warehouses, and related infrastructure that support manufacturing, shipping, and other large-scale economic activities.
-
C.
port area
chosen
A port area is a designated coastal or riverside zone equipped with infrastructure and facilities for the berthing, loading, unloading, storage, and transfer of cargo and passengers between land and water transport.
-
D.
inland port
An inland port is a logistics and transportation hub located away from coastal seaports, typically along rivers, canals, or rail corridors, that facilitates the transfer, storage, and distribution of goods between different modes of transport.
-
E.
former port city
A former port city is an urban settlement that once functioned as a significant maritime trade hub but has since lost its port operations or primary seafaring role due to economic, environmental, or infrastructural changes.
- 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_69d6ab4c6710819097a9d228382dde43 |
completed | April 8, 2026, 7:23 p.m. |
Created at: April 8, 2026, 9:50 p.m.