Triple
T18432561
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toll Road Investors Partnership II |
E450308
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | infrastructure investor group |
C16130
|
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: infrastructure investor group Context triple: [Toll Road Investors Partnership II, instanceOf, infrastructure investor group]
-
A.
infrastructure finance company
An infrastructure finance company is a financial institution that provides long-term funding, credit support, and advisory services for the development, operation, and maintenance of large-scale public and private infrastructure projects.
-
B.
private investment consortium
chosen
A private investment consortium is a group of non-public investors who pool capital and expertise to jointly finance, manage, and profit from selected investment opportunities.
-
C.
infrastructure developer
An infrastructure developer designs, builds, and maintains the underlying systems, tools, and automation that support reliable, scalable, and secure software deployment and operations.
-
D.
infrastructure management company
An infrastructure management company plans, operates, maintains, and optimizes physical assets and systems—such as transportation, utilities, and public works—to ensure their reliability, efficiency, and long-term performance.
-
E.
structural and investment fund
A structural and investment fund is a pooled financial vehicle designed to provide long-term capital for infrastructure, development, or strategic projects while optimizing risk-return profiles through diversified, often regulated, investment structures.
- 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_69d8d381d6388190a9e94e9c658174e4 |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:27 a.m.