Triple
T2959364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zwönitz |
E80007
|
entity |
| Predicate | hasHeadwaterRole |
P13535
|
FINISHED |
| Object | headstream of Chemnitz (river) |
—
|
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: headstream of Chemnitz (river) | Statement: [Zwönitz, hasHeadwaterRole, headstream of Chemnitz (river)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHeadwaterRole Context triple: [Zwönitz, hasHeadwaterRole, headstream of Chemnitz (river)]
-
A.
hasWaterwayRole
chosen
Indicates that an entity participates in or is associated with a waterway in a specific functional capacity or role.
-
B.
hasWatercourseType
Indicates the specific kind or category of watercourse (such as river, stream, or canal) associated with an entity.
-
C.
hasWatershed
Indicates that one geographic area or feature is part of, drains into, or is hydrologically defined by a particular watershed.
-
D.
hasStructureOnWatercourse
Indicates that a structure is physically located on, over, or directly associated with a specific watercourse.
-
E.
hasWatershedCharacteristic
Indicates that a watershed possesses a specified characteristic, feature, or property.
- 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_69ad8b1341848190bd19dbf46892887d |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad992c4c7c819084b5bef299255181 |
completed | March 8, 2026, 3:43 p.m. |
| PD | Predicate disambiguation | batch_69ad960c5c8881909d679912bd7d78f3 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:57 p.m.