Triple
T32487935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Puget Sound port system |
E830293
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional economic infrastructure |
C16082
|
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: regional economic infrastructure Context triple: [Puget Sound port system, instanceOf, regional economic infrastructure]
-
A.
regional economy
A regional economy is the interconnected system of production, consumption, labor, and trade within a specific geographic area, shaped by local resources, industries, institutions, and policies.
-
B.
regional economic zone
A regional economic zone is a geographically defined area within or across countries where economic policies, regulations, and incentives are coordinated to promote trade, investment, and development.
-
C.
regional economic cooperation framework
A regional economic cooperation framework is an organized arrangement among neighboring countries to coordinate policies, reduce trade and investment barriers, and promote shared economic development and integration.
-
D.
territorial economy
A territorial economy is an economic system organized and regulated within a specific geographic area, where production, distribution, and consumption are shaped by local resources, institutions, and spatial relationships.
-
E.
Infrastructure for trade
chosen
Infrastructure for trade encompasses the physical, digital, and institutional systems—such as transportation networks, ports, logistics hubs, communication technologies, and regulatory frameworks—that enable the efficient exchange of goods and services across regions and markets.
- 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_69f34920aa4081908d8fb0277414b911 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:58 a.m.