Triple
T36775598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stör Canal |
E908609
|
entity |
| Predicate | hasSourceWaterBody |
P25636
|
FINISHED |
| Object | Lake Schwerin |
—
|
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: Lake Schwerin | Statement: [Stör Canal, hasSourceWaterBody, Lake Schwerin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSourceWaterBody Context triple: [Stör Canal, hasSourceWaterBody, Lake Schwerin]
-
A.
hasAssociatedWaterBody
Indicates that one entity is linked to, or occurs in connection with, a specific body of water such as a river, lake, or sea.
-
B.
hasWaterResourceRole
Indicates that an entity participates in a water-related resource context with a specified functional role (e.g., source, user, manager, or regulator of water resources).
-
C.
hasBodyOfWaterType
Indicates that a body of water is classified as being of a particular type or category (such as lake, river, ocean, etc.).
-
D.
sourceOfWatercourse
chosen
Indicates that one entity is the origin or starting point from which a watercourse (such as a river or stream) begins or flows.
-
E.
hasWatersOf
Indicates that a geographic or physical entity contains, is traversed by, or is otherwise characterized by specific bodies or types of water.
- 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_69f76e798aa08190ace31098d1b13e9f |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fda5003cdc8190a558501271389912 |
completed | May 8, 2026, 8:55 a.m. |
| PD | Predicate disambiguation | batch_69fda05bfc2c819096821a5300e9bb24 |
completed | May 8, 2026, 8:35 a.m. |
Created at: May 3, 2026, 4:12 p.m.