Triple
T13273343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wesco Financial Corporation |
E316123
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Berkshire Hathaway subsidiary |
C32757
|
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: Berkshire Hathaway subsidiary Context triple: [Wesco Financial Corporation, instanceOf, Berkshire Hathaway subsidiary]
-
A.
Alphabet Inc. subsidiary
An Alphabet Inc. subsidiary is a legally distinct company that is majority-owned and controlled by Alphabet Inc., operating under its corporate umbrella while maintaining its own management and operations.
-
B.
Airbus subsidiary
An Airbus subsidiary is a legally distinct company that is owned or controlled by Airbus and operates specific aspects of its aerospace, defense, or related business activities.
-
C.
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.
-
D.
Toyota subsidiary
A Toyota subsidiary is a legally distinct company in which Toyota Motor Corporation holds a controlling interest, operating under its strategic direction while managing specific regional markets, product lines, or business functions.
-
E.
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.
- 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_69d806b1d9ac8190852c5571d5bd5f0f |
completed | April 9, 2026, 8:06 p.m. |
Created at: April 9, 2026, 9:26 p.m.