Triple
T25298409
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Griebnitz Canal |
E634279
|
entity |
| Predicate | hasWaterwayClass |
P17791
|
FINISHED |
| Object | regional waterway |
—
|
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: regional waterway | Statement: [Griebnitz Canal, hasWaterwayClass, regional waterway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWaterwayClass Context triple: [Griebnitz Canal, hasWaterwayClass, regional waterway]
-
A.
hasWatercourseType
Indicates the specific kind or category of watercourse (such as river, stream, or canal) associated with an entity.
-
B.
waterwayClass
chosen
Indicates the classification or type of a waterway based on its navigational, functional, or physical characteristics.
-
C.
hasWaterwayRole
Indicates that an entity participates in or is associated with a waterway in a specific functional capacity or role.
-
D.
isWaterway
Indicates that one entity is a water-based route or channel (such as a river, canal, or sea lane) used for travel or transport.
-
E.
isInWaterwaySystem
Indicates that an entity is part of, contained within, or traverses a particular waterway network or system.
- 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_69e75a9503d48190b80a005c6af0cb50 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f5ffc74fa481909b4fe24a9337f9eb |
completed | May 2, 2026, 1:44 p.m. |
| PD | Predicate disambiguation | batch_69f5f7f99dc08190afcfb3bc4dfbec1d |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 21, 2026, 1:22 p.m.