Triple
T34120993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Himmelpforten |
E875129
|
entity |
| Predicate | locatedNearHydrologicalFeature |
P8567
|
FINISHED |
| Object | Möhne River |
E300533
|
NE 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: Möhne River | Statement: [Himmelpforten, locatedNearHydrologicalFeature, Möhne River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedNearHydrologicalFeature Context triple: [Himmelpforten, locatedNearHydrologicalFeature, Möhne River]
-
A.
nearbyWatercourse
chosen
Indicates that one entity is located close to or alongside a natural or artificial watercourse, such as a river, stream, or canal.
-
B.
riverTypeNearby
Indicates that one entity is located near a river of a specified type or classification.
-
C.
riverLocation
Indicates that a river is located in, passes through, or is geographically associated with a specified place or region.
-
D.
riverineLocation
Indicates that something is located in, along, or directly associated with a river or river system.
-
E.
locatedOnTributaryOf
Indicates that one entity is situated along or on the banks of a tributary that flows into another specified water body.
- F. None of above.
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_69f349a9271c81909576994c9ef7b179 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a375bc4f7108190aefaf59c1a4824d5 |
completed | June 21, 2026, 3:34 a.m. |
| PD | Predicate disambiguation | batch_6a0379f963908190846d232f386fd98f |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:53 a.m.