Triple
T25222179
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nes aan de Amstel |
E631993
|
entity |
| Predicate | hasNearbyWaterManagementStructure |
P62654
|
FINISHED |
| Object | polders and dikes |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: polders and dikes | Statement: [Nes aan de Amstel, hasNearbyWaterManagementStructure, polders and dikes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyWaterManagementStructure Context triple: [Nes aan de Amstel, hasNearbyWaterManagementStructure, polders and dikes]
-
A.
hasWaterManagementStructure
chosen
Indicates that one entity possesses, contains, or is associated with a built feature used to control, store, convey, or manage water.
-
B.
hasNearbyWaterInfrastructure
Indicates that a location or entity is situated close to water-related infrastructure such as pipes, treatment facilities, or distribution systems.
-
C.
hasNearbyWaterBoard
Indicates that an entity is located close to, or within the jurisdictional area of, a water management or water regulatory board.
-
D.
hasNearbyWater
Indicates that one entity is located close to a body of water associated with or relevant to another entity.
-
E.
hasNearbyRiverStructure
Indicates that a river-related structure (such as a dam, bridge, or levee) is located close to the referenced entity.
- F. None of above.
Provenance (3 batches)
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_69e75a8e0f688190a7aebe9a4815e25b |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f6640168948190811bd5f933a87cf5 |
completed | May 2, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69f6633451948190bcc0410602bb4914 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 21, 2026, 1:03 p.m.