Triple
T26649530
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tuas Biomedical Park |
E669013
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | biomedical industrial estate |
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: biomedical industrial estate Context triple: [Tuas Biomedical Park, instanceOf, biomedical industrial estate]
-
A.
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.
-
B.
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.
-
C.
commercial and industrial complex
A commercial and industrial complex is a large, planned development that integrates multiple business, retail, and manufacturing or warehousing facilities within a shared infrastructure and site.
-
D.
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.
-
E.
EIT Manufacturing Co-Location Centre
EIT Manufacturing Co-Location Centre is a regional hub that connects industry, academia, and innovators to collaborate on, develop, and deploy advanced manufacturing solutions within the EIT Manufacturing ecosystem.
- 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_69ee9d00eb5481908d6c6d0ada2f0c9a |
completed | April 26, 2026, 11:17 p.m. |
Created at: April 27, 2026, 2:32 a.m.