Triple
T30317171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MIT Investment Management Company |
E771088
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | investment management organization |
C18415
|
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: investment management organization Context triple: [MIT Investment Management Company, instanceOf, investment management organization]
-
A.
investment organization
chosen
An investment organization is an entity that pools and manages financial resources to allocate capital into various assets or ventures with the goal of generating returns for its stakeholders.
-
B.
private investment and management company
A private investment and management company is a firm that deploys its own or clients’ capital into various assets while actively overseeing, optimizing, and strategically guiding those investments to generate long-term returns.
-
C.
investment management software provider
An investment management software provider develops and delivers digital tools that help financial professionals and institutions plan, execute, monitor, and optimize investment portfolios and related operations.
-
D.
quantitative investment firm
A quantitative investment firm is a financial institution that uses mathematical models, statistical analysis, and algorithmic strategies to make data-driven trading and investment decisions.
-
E.
wealth management provider
A wealth management provider is a financial services entity that offers personalized investment, financial planning, and advisory solutions to help clients grow, preserve, and transfer their wealth.
- 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_69f22488f224819081b0f3ec41ab975c |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7:51 p.m.