Triple
T34489409
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kulim Hi-Tech Park free industrial zone |
E885424
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | free industrial zone |
C6465
|
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: free industrial zone Context triple: [Kulim Hi-Tech Park free industrial zone, instanceOf, free industrial zone]
-
A.
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.
-
B.
industrial park
chosen
An industrial park is a planned and zoned area of land designated for industrial development, typically providing shared infrastructure, utilities, and transportation access for manufacturing, warehousing, and related businesses.
-
C.
industrial district
An industrial district is a designated urban or regional area characterized by a high concentration of manufacturing, warehousing, and related industrial activities supported by specialized infrastructure and services.
-
D.
free zone administrative authority
A free zone administrative authority is the governing body responsible for regulating, managing, and promoting operations within a designated free trade or special economic zone.
-
E.
free territory
A free territory is a geographically defined area where inhabitants exercise a high degree of political autonomy or self-governance, often independent from or only loosely subject to external state control.
- 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_69f349cafcec8190997b45b3fdc16c27 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 2:01 a.m.