Triple
T8603391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jinqiao Export Processing Zone |
E203734
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | export processing zone |
C24707
|
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: export processing zone Context triple: [Jinqiao Export Processing Zone, instanceOf, export processing zone]
-
A.
protective zone
A protective zone is a designated area or boundary established to shield people, assets, or environments from potential harm, hazards, or unauthorized influence.
-
B.
infrastructure development zone
An infrastructure development zone is a designated geographic area prioritized for the planning, investment, and construction of essential public facilities and services—such as transportation, utilities, and communications—to support economic growth and urban or regional development.
-
C.
transition zone
A transition zone is a boundary region where two distinct systems, phases, or environments meet and gradually change into one another, exhibiting mixed or intermediate characteristics.
-
D.
no-take zone
A no-take zone is a designated area, typically in a marine or freshwater environment, where all forms of extractive activities such as fishing, mining, and harvesting are strictly prohibited to protect ecosystems and biodiversity.
-
E.
emissions control zone
An emissions control zone is a designated geographic area where stricter limits on air pollutants are enforced to reduce environmental and health impacts from sources such as vehicles, ships, and industrial activities.
- F. None of above. chosen
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_69ca832b56948190ba751cec255308f1 |
completed | March 30, 2026, 2:05 p.m. |
Created at: March 30, 2026, 6:24 p.m.