Triple
T35568679
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northern California defense-related industrial corridor |
E1027849
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional economic cluster |
C44546
|
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 cluster Context triple: [Northern California defense-related industrial corridor, instanceOf, regional economic cluster]
-
A.
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.
-
B.
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.
-
C.
regional industry
chosen
A regional industry is a network of related businesses, suppliers, and supporting institutions concentrated in a specific geographic area that collectively produce similar or complementary goods or services.
-
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.
regional center
A regional center is an organization or facility that provides specialized services, coordination, and support to a defined geographic area, often acting as a hub for resources, administration, or expertise.
- 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_69f76e020fd8819081cb080e7e203083 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:04 p.m.