Triple
T4961352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maasvlakte 2 |
E111414
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | port expansion project |
C2938
|
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: port expansion project Context triple: [Maasvlakte 2, instanceOf, port expansion project]
-
A.
infrastructure project
chosen
An infrastructure project is a large-scale, organized effort to plan, design, and construct foundational physical systems—such as transportation, utilities, and public facilities—that support a community’s or region’s economic and social activities.
-
B.
light rail expansion project
A light rail expansion project is a coordinated planning, design, and construction effort to extend an existing light rail transit system’s routes, capacity, and supporting infrastructure to serve additional areas and riders.
-
C.
healthcare facility expansion program
A healthcare facility expansion program is a coordinated initiative to increase a medical institution’s capacity, services, and infrastructure to better meet current and future patient care needs.
-
D.
Long Island Rail Road project
A Long Island Rail Road project is a coordinated initiative to plan, construct, upgrade, or maintain LIRR infrastructure, services, or operations to improve rail transportation for its riders and communities.
-
E.
public transit and highway improvement program
A public transit and highway improvement program is a coordinated set of projects and policies designed to enhance the capacity, safety, efficiency, and accessibility of transportation networks through upgrades to roads, highways, and mass transit systems.
- 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_69bd4419393c819086319a6fe4bf8542 |
completed | March 20, 2026, 12:56 p.m. |
Created at: March 20, 2026, 1:32 p.m.