Triple
T16778190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zhongguancun Science Park |
E407784
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | high-tech industrial park |
C908
|
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: high-tech industrial park Context triple: [Zhongguancun Science Park, instanceOf, high-tech industrial park]
-
A.
industrial park
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.
-
B.
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.
-
C.
industrial and residential complex
A mixed-use development that integrates industrial facilities with residential housing, designed to support both production activities and everyday living within a coordinated, shared environment.
-
D.
research park
chosen
A research park is a planned development that clusters research institutions, high-tech companies, and support facilities to foster innovation, collaboration, and technology commercialization.
-
E.
commercial park
A commercial park is a planned area of land developed with multiple business facilities—such as offices, retail spaces, and light industrial units—designed to support commercial activities within a cohesive, often landscaped environment.
- 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_69d8839270588190886720d9519bbf8f |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:22 a.m.