Triple
T25893977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kesteren |
E652412
|
entity |
| Predicate | hasRiverDike |
P127358
|
FINISHED |
| Object | Nederrijn dike near Kesteren |
—
|
NE NERFINISHED |
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: Nederrijn dike near Kesteren | Statement: [Kesteren, hasRiverDike, Nederrijn dike near Kesteren]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRiverDike Context triple: [Kesteren, hasRiverDike, Nederrijn dike near Kesteren]
-
A.
DikeRepresents
Indicates that one entity (typically a person or organization) serves as the legal representative or advocate for another entity in matters concerning a dike or flood-defense structure.
-
B.
dikeBreaches
Indicates that a dike fails or ruptures, allowing water to break through its barrier.
-
C.
watercourseHasDam
Indicates that a watercourse (such as a river or stream) has a dam constructed on or across it.
-
D.
hasRiver
Indicates that a location or area contains, is traversed by, or is directly associated with a river.
-
E.
hasNearbyRiverStructure
chosen
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_69e7ab3c6cc081908de59bfcc28ec19d |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6430a93a48190854ce71df680b2fa |
completed | May 2, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69f641da05b881909f6283c988639c53 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 22, 2026, 8:22 a.m.