Triple
T34607320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aduard (former municipality) |
E888628
|
entity |
| Predicate | waterwayConnectionVia |
P27579
|
FINISHED |
| Object | Hoendiep |
—
|
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: Hoendiep | Statement: [Aduard (former municipality), waterwayConnectionVia, Hoendiep]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterwayConnectionVia Context triple: [Aduard (former municipality), waterwayConnectionVia, Hoendiep]
-
A.
waterwayLinkBetween
Indicates a connection or linkage between two waterways, such as rivers, canals, or channels, through which water can flow or navigation can occur.
-
B.
waterwayServed
Indicates that a place, facility, or infrastructure is served by, connected to, or functionally supported by a particular waterway.
-
C.
waterwayJunction
Indicates a point where two or more waterways meet, intersect, or branch from one another.
-
D.
waterwayThrough
chosen
Indicates that a waterway (such as a river or canal) passes through or traverses a specified geographic area or feature.
-
E.
usesWaterwaysFor
Indicates that one entity relies on or employs waterways as a means or route to perform an activity or function in relation to another 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_69f349d489d48190ba30e7d97c6f5ef9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd8ccbd4c88190b13aae0673b3c821 |
completed | May 8, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69fd8ae2227c819089546f5c3629799e |
completed | May 8, 2026, 7:04 a.m. |
Created at: May 1, 2026, 2:03 a.m.