Triple
T37067582
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thor Park |
E917489
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | technology and science 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: technology and science park Context triple: [Thor Park, instanceOf, technology and science park]
-
A.
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.
-
B.
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.
-
C.
science and business campus
A science and business campus is an integrated environment where research facilities, academic institutions, and commercial enterprises co-locate to foster innovation, collaboration, and the translation of scientific discoveries into marketable solutions.
-
D.
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.
-
E.
science and education center
A science and education center is a facility dedicated to promoting scientific literacy and learning through interactive exhibits, educational programs, and research-supporting resources for students and the public.
- 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_69f76e95fa40819091e14681087ae5e4 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:14 p.m.