Triple
T36775611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stör Canal |
E908609
|
entity |
| Predicate | waterBodyTypeServed |
P196380
|
FINISHED |
| Object | lake |
—
|
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: lake | Statement: [Stör Canal, waterBodyTypeServed, lake]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterBodyTypeServed Context triple: [Stör Canal, waterBodyTypeServed, lake]
-
A.
watercourseTypeServed
Indicates the type of watercourse (e.g., river, canal, stream) that is supplied, supported, or otherwise served by a given feature or system.
-
B.
waterbodyUsedFor
Indicates that a particular water body is utilized for a specific purpose, activity, or function.
-
C.
waterwayServed
Indicates that a place, facility, or infrastructure is served by, connected to, or functionally supported by a particular waterway.
-
D.
hostedOnWaterBodyType
Indicates that an event, activity, or entity takes place on or is situated upon a specific type of water body (e.g., lake, river, ocean).
-
E.
appliesToWaterBody
Indicates that something (such as a rule, condition, property, or effect) is relevant or applicable specifically to a particular water body.
- F. None of above. chosen
Provenance (4 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_69fe2f078c24819082ba396b56f02808 |
completed | May 8, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69fe228fe1988190baf3bb34897f3dbe |
completed | May 8, 2026, 5:51 p.m. |
| PDg | Predicate description generation | batch_69fe2f066ac48190882c327b7e69e53f |
completed | May 8, 2026, 6:44 p.m. |
Created at: May 3, 2026, 4:12 p.m.