Triple
T4621901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BlueCo 22 Limited |
E101004
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | private investment consortium |
C16130
|
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: private investment consortium Context triple: [BlueCo 22 Limited, instanceOf, private investment consortium]
-
A.
private consortium
A private consortium is a collaborative alliance of independent, typically private-sector organizations that pool resources, expertise, and decision-making authority to pursue shared objectives while remaining legally distinct entities.
-
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.
multinational consortium
A multinational consortium is a collaborative alliance of independent organizations from multiple countries that pool resources, expertise, and risks to pursue shared objectives or large-scale projects.
-
D.
business consortium
A business consortium is a collaborative association of independent companies that pool resources, expertise, or capital to pursue shared objectives, projects, or market opportunities while retaining their individual autonomy.
-
E.
private equity fund
A private equity fund is an investment vehicle that pools capital from institutional and accredited investors to acquire, restructure, and eventually exit ownership stakes in private (or privatized) companies for long-term capital appreciation.
- F. None of above. chosen
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_69bd43d0497c8190ac23c65c5804846a |
completed | March 20, 2026, 12:55 p.m. |
Created at: March 20, 2026, 1:12 p.m.