Triple
T25536081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hansweert |
E640041
|
entity |
| Predicate | hasSeaDyke |
P27578
|
FINISHED |
| Object | Western Scheldt dyke at Hansweert |
—
|
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: Western Scheldt dyke at Hansweert | Statement: [Hansweert, hasSeaDyke, Western Scheldt dyke at Hansweert]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSeaDyke Context triple: [Hansweert, hasSeaDyke, Western Scheldt dyke at Hansweert]
-
A.
hasHighwayAlongShore
Indicates that a highway runs adjacent to or closely follows the shoreline of a body of water.
-
B.
hasEmbankment
chosen
Indicates that one entity possesses or is characterized by an embankment, such as a raised structure built to contain, support, or protect against water or terrain.
-
C.
hasSeaAccess
Indicates that an entity has direct access to the sea, typically via a coastline, port, or navigable waterway connected to the sea.
-
D.
hasMarinaOrStaithe
Indicates that a place includes or is associated with a marina or staithe (a landing stage or mooring area for boats).
-
E.
hasBreakwater
Indicates that a structure or location is equipped with or associated with a breakwater that provides protection from waves or erosion.
- 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_69e75dbfff7081909b0aa779d48321d2 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f6cee45590819086e489bfccbe4ac3 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1188708190b8f0f56e595e6057 |
completed | May 3, 2026, 4:16 a.m. |
Created at: April 21, 2026, 3:22 p.m.