Triple
T13935982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MIT entrepreneurship ecosystem |
E335123
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | entrepreneurship ecosystem |
C7288
|
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: entrepreneurship ecosystem Context triple: [MIT entrepreneurship ecosystem, instanceOf, entrepreneurship ecosystem]
-
A.
startup ecosystem
chosen
A startup ecosystem is a dynamic network of entrepreneurs, investors, institutions, resources, and support organizations that interact within a region or sector to create, grow, and scale new ventures.
-
B.
innovation and entrepreneurship space
A dynamic, collaborative environment that provides resources, mentorship, and networking opportunities to help individuals and teams develop, test, and launch innovative ideas and entrepreneurial ventures.
-
C.
entrepreneurship support program
An entrepreneurship support program is an organized set of resources, services, and activities designed to help aspiring and existing entrepreneurs develop, launch, and grow their ventures.
-
D.
software and services ecosystem
A software and services ecosystem is an interconnected network of applications, platforms, tools, and providers that collaboratively deliver integrated digital capabilities and value to users and organizations.
-
E.
startup accelerator program
A startup accelerator program is a fixed-term, cohort-based initiative that provides early-stage companies with mentorship, resources, networking, and often seed funding in exchange for equity to rapidly grow their businesses.
- 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_69d81c5f739081908bc05b2461f54828 |
completed | April 9, 2026, 9:38 p.m. |
Created at: April 9, 2026, 10:17 p.m.