Triple
T21840292
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ABG |
E539235
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | intellectual property holding company |
C38035
|
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: intellectual property holding company Context triple: [ABG, instanceOf, intellectual property holding company]
-
A.
intellectual property management organization
chosen
An intellectual property management organization is an entity that helps creators and businesses protect, administer, license, and enforce their intellectual property rights to maximize legal security and commercial value.
-
B.
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.
-
C.
business holding company
A business holding company is a legal entity that owns controlling interests in other companies’ shares or assets, primarily to manage, oversee, and coordinate their operations and strategic direction without directly producing goods or services itself.
-
D.
publicly traded holding company
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.
-
E.
ownership company
An ownership company is a legal entity that holds and manages ownership stakes in assets or other businesses, exercising control and deriving benefits from those holdings.
- 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_69e0c476c3c88190a92d08ebb59a128a |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:55 p.m.