Triple
T24671813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hoedekenskerke |
E610857
|
entity |
| Predicate | hasSeaOrOcean |
P2040
|
FINISHED |
| Object | North Sea (via Western Scheldt) |
—
|
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: North Sea (via Western Scheldt) | Statement: [Hoedekenskerke, hasSeaOrOcean, North Sea (via Western Scheldt)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSeaOrOcean Context triple: [Hoedekenskerke, hasSeaOrOcean, North Sea (via Western Scheldt)]
-
A.
hasOcean
chosen
Indicates that a geographic region, country, or landmass is bordered by or directly adjacent to a particular ocean.
-
B.
hasOceanType
Indicates that a body of water is classified as belonging to a particular type of ocean or oceanic category.
-
C.
hasNotableSea
Indicates that an entity is associated with or contains a sea that is considered notable or significant.
-
D.
hasOceanCoverage
Indicates that a specified area or region is covered by ocean to a certain extent or proportion.
-
E.
hasOceanTerminusIn
Indicates that something such as a river or waterway ends or flows into the specified ocean.
- 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_69e2c4d505cc8190981881df06c0bf52 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f41011d8048190be70329ba0bfb7c7 |
completed | May 1, 2026, 2:29 a.m. |
| PD | Predicate disambiguation | batch_69f40ed9d47881909fcfc0d04e8d074a |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 2:46 a.m.