Triple
T12306526
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brigade Tech Park |
E293366
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | IT business park |
C20975
|
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: IT business park Context triple: [Brigade Tech Park, instanceOf, IT business 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.
commercial park
chosen
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.
-
C.
IBM facility
An IBM facility is a physical location owned or operated by IBM where the company conducts its business activities, such as research, development, manufacturing, data center operations, or corporate services.
-
D.
business loop
A business loop is a special type of highway or road segment that departs from a main route to pass through the commercial center of a town or city before reconnecting with the primary roadway.
-
E.
information and communications technology hub
An information and communications technology hub is a centralized environment—physical, virtual, or hybrid—where ICT infrastructure, services, expertise, and innovation converge to support connectivity, digital operations, and technological development for organizations and communities.
- 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_69d6ab6a2b50819082f6aedd32ed608a |
completed | April 8, 2026, 7:24 p.m. |
Created at: April 8, 2026, 9:53 p.m.