Triple
T3470842
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dulles Technology Corridor |
E73254
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | technology business district |
C26
|
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 business district Context triple: [Dulles Technology Corridor, instanceOf, technology business district]
-
A.
technology region
chosen
A technology region is a geographically defined area characterized by a high concentration of technology-related activities, infrastructure, companies, and talent that collectively drive innovation and economic growth.
-
B.
urban business district
An urban business district is a densely developed area within a city characterized by a high concentration of offices, commercial activities, financial institutions, and supporting services that form the economic core of the urban environment.
-
C.
technology alliance
A technology alliance is a strategic partnership between organizations that collaborate to develop, share, or integrate technological resources, expertise, and innovations to achieve mutual goals.
-
D.
technology investor
A technology investor is an individual or entity that allocates capital to technology-focused companies or innovations with the expectation of financial returns driven by technological advancement and market growth.
-
E.
technology investor
A technology investor is an individual or entity that allocates capital to technology-focused companies or innovations with the expectation of achieving financial returns through growth, innovation, and market disruption.
- 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_69ad85b2fed48190948c8765e453d270 |
completed | March 8, 2026, 2:20 p.m. |
Created at: March 8, 2026, 3:17 p.m.