Triple
T28928325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fulda |
E733711
|
entity |
| Predicate | meetsWerraAt |
P157273
|
FINISHED |
| Object | Hann. Münden |
—
|
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: Hann. Münden | Statement: [Fulda, meetsWerraAt, Hann. Münden]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: meetsWerraAt Context triple: [Fulda, meetsWerraAt, Hann. Münden]
-
A.
joinsRiverNear
chosen
Indicates that one river or watercourse flows into and merges with another river at or close to a specified location.
-
B.
locatedAtConfluenceOf
Indicates that something is situated at the meeting point where two or more bodies of water or similar flowing features join together.
-
C.
meetsWaterway
Indicates that one geographic feature or entity comes into contact with or joins a waterway such as a river, canal, or stream.
-
D.
hasHeadwatersIn
Indicates that the source or origin of a river, stream, or similar watercourse is located within a specified geographic area or feature.
-
E.
hasHeadwatersOf
Indicates that a specified location or feature is the source or origin point of a particular river or watercourse.
- 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_69f05b0b49b08190b8994b339c7980f6 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f65b50b3d081908d4164f0506236d6 |
completed | May 2, 2026, 8:15 p.m. |
| PD | Predicate disambiguation | batch_69f659d02f1c8190831758ac52bb54e4 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 8:25 a.m.