Triple
T30941144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eggegebirge |
E788262
|
entity |
| Predicate | drainageToRiver |
P4497
|
FINISHED |
| Object | Weser |
—
|
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: Weser | Statement: [Eggegebirge, drainageToRiver, Weser]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: drainageToRiver Context triple: [Eggegebirge, drainageToRiver, Weser]
-
A.
hasBodyOfWaterDrainedBy
Indicates that a body of water is emptied or its water flow is carried away by a specified draining feature, such as a river, channel, or drainage system.
-
B.
drainsInto
chosen
Indicates that one entity serves as a source or conduit whose contents or flow are directed into another entity.
-
C.
drainageDivideOf
Indicates that one geographic feature functions as the drainage divide (separating water flow into different basins) for another feature or area.
-
D.
reservoirRiver
Indicates that a reservoir is supplied or drained by, and thus hydrologically connected to, a particular river.
-
E.
isWatercourseOf
Indicates that a watercourse (such as a river or stream) flows through, belongs to, or is geographically associated with a particular area or feature.
- 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_69f224c180f88190ad177372ee02b7e2 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ed5d008190831cf8e44cce28af |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 29, 2026, 8:53 p.m.