Triple
T25270082
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Austrian Southern Railway Company |
E633544
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | joint‑stock company |
C18899
|
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: joint‑stock company Context triple: [Austrian Southern Railway Company, instanceOf, joint‑stock company]
-
A.
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.
-
B.
for-profit corporation
chosen
A for-profit corporation is a legally recognized business entity formed to conduct commercial activities with the primary goal of generating profits for its owners or shareholders.
-
C.
special share company
A special share company is a corporate entity structured to issue a distinct class of shares with unique rights or restrictions—often for control, regulatory, or strategic purposes—differing from ordinary equity.
-
D.
Limited liability company
A limited liability company (LLC) is a business structure that combines the limited liability protection of a corporation with the pass-through taxation and operational flexibility of a partnership or sole proprietorship.
-
E.
company
A company is an organized entity, legally recognized or informally structured, that coordinates people and resources to produce goods or services for customers, typically in pursuit of profit or specific objectives.
- 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_69e75a92f48881909974ff9c11150a2e |
completed | April 21, 2026, 11:08 a.m. |
Created at: April 21, 2026, 1:16 p.m.