Triple
T8816265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haarlemmermeer drainage project |
E209784
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | land reclamation project |
C22840
|
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: land reclamation project Context triple: [Haarlemmermeer drainage project, instanceOf, land reclamation project]
-
A.
land reclamation campaign
A land reclamation campaign is a coordinated effort, typically led by governments or organizations, to convert unusable or degraded land—such as wetlands, deserts, or polluted areas—into productive land for agriculture, industry, housing, or environmental restoration.
-
B.
reclaimed island
chosen
A reclaimed island is an artificial landmass created by filling in bodies of water, such as seas, lakes, or rivers, with earth, sand, or other materials to form usable land for human activities.
-
C.
infrastructure project
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.
-
D.
waterfront development site
A waterfront development site is a designated parcel of land adjacent to a body of water that is planned or suitable for construction and mixed-use projects leveraging water access and views.
-
E.
waterfront revitalization plan
A waterfront revitalization plan is a comprehensive strategy to transform underused or deteriorated shoreline areas into vibrant, accessible, and sustainable public and economic spaces.
- 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_69ca8364e13081909c85fe80f44fe86f |
completed | March 30, 2026, 2:06 p.m. |
Created at: March 30, 2026, 6:45 p.m.