Triple
T26840661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coimbatore SEZ |
E675766
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Special Economic Zone |
C5706
|
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: Special Economic Zone Context triple: [Coimbatore SEZ, instanceOf, Special Economic Zone]
-
A.
special economic zone
chosen
A special economic zone is a designated geographic area within a country where business and trade laws differ from the rest of the nation to attract investment, boost exports, and stimulate economic growth.
-
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.
economic and technological development zone
An economic and technological development zone is a designated area where governments concentrate infrastructure, incentives, and regulatory support to attract investment, foster industrial innovation, and accelerate regional economic growth.
-
D.
multi-island economic zone
A multi-island economic zone is a geographically dispersed but administratively unified area spanning multiple islands, designed to coordinate infrastructure, trade, and investment policies to stimulate regional economic development.
-
E.
free trade zone
A free trade zone is a designated geographic area within a country where goods can be imported, stored, processed, and re-exported with reduced or eliminated customs duties and regulatory barriers to promote trade and investment.
- 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_69eee9b8d5e88190a07d3455c0fbb21f |
completed | April 27, 2026, 4:44 a.m. |
Created at: April 27, 2026, 5:07 a.m.