Triple
T32715435
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CCR Ponte |
E836509
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | infrastructure concession company |
C6258
|
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 concession company Context triple: [CCR Ponte, instanceOf, infrastructure concession company]
-
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.
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.
-
C.
transport infrastructure operator
A transport infrastructure operator is an entity responsible for managing, maintaining, and regulating transportation networks and facilities such as roads, railways, ports, or airports to ensure safe and efficient movement of people and goods.
-
D.
toll road operator
chosen
A toll road operator is an entity responsible for managing, maintaining, and collecting user fees on designated roadways or bridges, often under government concession or private ownership.
-
E.
transportation network company
A transportation network company is a business that uses digital platforms, typically mobile apps, to connect passengers with drivers who provide on-demand transportation services.
- 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_69f34935455881909088975d79460418 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:11 a.m.