Triple
T5502026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Freight Operating Companies |
E144350
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | type of business entity |
C19105
|
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: type of business entity Context triple: [Freight Operating Companies, instanceOf, type of business entity]
-
A.
corporate legal form
A corporate legal form is a legally recognized organizational structure that defines a corporation’s rights, responsibilities, governance, and liability in conducting business.
-
B.
type of legal instrument
A type of legal instrument is a category of formally recognized documents or mechanisms, such as contracts, statutes, or wills, that create, modify, or extinguish legal rights and obligations.
-
C.
public-law corporation
A public-law corporation is a legal entity created by a government statute to perform specific public functions or services, operating with a degree of autonomy but subject to public law and governmental oversight.
-
D.
legal entity form under European Union law
A legal entity form under European Union law is a standardized organizational structure, such as an SE or SCE, created by EU legislation to enable companies or associations to operate across member states under a unified legal framework.
-
E.
special purpose entity
A special purpose entity is a legally separate organization created by a parent company to isolate financial risk, hold specific assets or liabilities, or conduct narrowly defined activities, often for financing or regulatory purposes.
- 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_69c008f5a2748190bce7a39aabf87a6d |
completed | March 22, 2026, 3:21 p.m. |
Created at: March 22, 2026, 3:32 p.m.