Triple
T4484193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brouwershavense Gat |
E107195
|
entity |
| Predicate | waterBodySystem |
P1011
|
FINISHED |
| Object | North Sea coastal system |
—
|
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: North Sea coastal system | Statement: [Brouwershavense Gat, waterBodySystem, North Sea coastal system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterBodySystem Context triple: [Brouwershavense Gat, waterBodySystem, North Sea coastal system]
-
A.
bodyOfWater
Indicates that one entity is a body of water that is geographically or physically associated with another entity.
-
B.
waterbodyID
Indicates a unique identifier that links an entity to a specific body of water.
-
C.
connectedBodyOfWater
Indicates that two geographic locations are linked by a continuous body of water through which water can flow between them.
-
D.
waterbodyType
chosen
Indicates the classification of a water body according to its type (e.g., river, lake, ocean, etc.).
-
E.
waterbodyUsedFor
Indicates that a particular water body is utilized for a specific purpose, activity, or function.
- 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_69bd43f84f788190a1383579c4a595be |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd556d29f08190bab1e872dd7e819f |
completed | March 20, 2026, 2:10 p.m. |
| PD | Predicate disambiguation | batch_69bd5213e3d0819094b026989e686f01 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 12:58 p.m.