Triple
T16806504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nagoya business community |
E408495
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional economic network |
C10807
|
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 network Context triple: [Nagoya business community, instanceOf, regional economic network]
-
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 collaborative network
chosen
A regional collaborative network is a structured alliance of organizations, institutions, and stakeholders within a specific geographic area that coordinate resources, knowledge, and activities to address shared goals and regional challenges.
-
C.
regional economic integration protocol
A regional economic integration protocol is a formal agreement among neighboring or closely linked countries that coordinates trade, investment, and regulatory policies to reduce barriers and promote a more unified regional market.
-
D.
regional partnership
A regional partnership is a collaborative alliance among organizations, governments, or stakeholders within a specific geographic area to coordinate resources, strategies, and initiatives toward shared economic, social, or environmental goals.
-
E.
regional axis
A regional axis is a conceptual line or direction that organizes, connects, or structures spatial relationships and activities across a defined geographic region.
- 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_69d88393905081908d00a86b99996ac8 |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:22 a.m.