Triple
T2603740
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Highways |
E58605
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | infrastructure operator |
C6404
|
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 operator Context triple: [National Highways, instanceOf, infrastructure operator]
-
A.
transport infrastructure operator
chosen
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.
-
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.
railway infrastructure manager
A railway infrastructure manager is an entity responsible for the planning, construction, maintenance, operation, and safe management of railway tracks, signaling systems, and related fixed installations.
-
D.
infrastructure
Infrastructure is the foundational physical and organizational systems—such as transportation, utilities, communication networks, and public facilities—that enable a society or organization to function and grow.
-
E.
television network operator
A television network operator is an organization that manages, schedules, and distributes television programming across broadcast, cable, satellite, or digital platforms to reach viewers.
- 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_69ab4ac3523881909679750c9f8c2dec |
completed | March 6, 2026, 9:44 p.m. |
Created at: March 6, 2026, 9:49 p.m.