Triple
T4672170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Icahn Enterprises |
E103589
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | publicly traded 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: publicly traded holding company Context triple: [Icahn Enterprises, instanceOf, publicly traded holding company]
-
A.
Privately held company
A privately held company is a business entity owned by a small group of individuals or organizations whose shares are not publicly traded on stock exchanges.
-
B.
retail holding company
A retail holding company is a parent corporation that owns and oversees multiple retail businesses or brands, managing their strategic direction and financial performance while each operates as a separate entity.
-
C.
airline holding company
An airline holding company is a parent corporation that owns and controls one or more airline carriers and related aviation businesses, managing strategy and finances while allowing the individual airlines to operate with some autonomy.
-
D.
multinational utility company
A multinational utility company is a large-scale enterprise that provides essential services such as electricity, gas, water, or telecommunications across multiple countries, operating under diverse regulatory, cultural, and market conditions.
-
E.
railway holding company
A railway holding company is a parent corporation that owns and controls one or more railway operating or infrastructure companies, managing their strategic direction and financial interests without necessarily running day-to-day train operations itself.
- 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_69bd43dda32c8190938b37744ca270fc |
completed | March 20, 2026, 12:55 p.m. |
Created at: March 20, 2026, 1:15 p.m.