Triple
T14060989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beijing Capital Group |
E338343
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | investment holding company |
C16160
|
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 holding company Context triple: [Beijing Capital Group, instanceOf, investment holding company]
-
A.
industrial holding company
An industrial holding company is a parent corporation that owns controlling interests in multiple industrial or manufacturing businesses, managing them strategically while typically leaving day-to-day operations to subsidiary management.
-
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.
publicly traded holding company
chosen
A publicly traded holding company is a corporation whose primary business is owning controlling interests in other companies, with its shares available for purchase on public stock exchanges.
-
D.
investment organization
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.
-
E.
investment arm
An investment arm is a dedicated division or entity within a larger organization that manages and deploys capital into various assets, ventures, or companies to generate financial returns and strategic value.
- 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_69d81c67ba6c819091935650dfb3b895 |
completed | April 9, 2026, 9:38 p.m. |
Created at: April 9, 2026, 10:21 p.m.