Triple
T21345490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fränkische Saale |
E526322
|
entity |
| Predicate | flowsThrough |
P225
|
FINISHED |
| Object | Hammelburg |
—
|
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: Hammelburg | Statement: [Fränkische Saale, flowsThrough, Hammelburg]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hammelburg Context triple: [Fränkische Saale, flowsThrough, Hammelburg]
-
A.
Hammelburg
chosen
Hammelburg is a historic town in northern Bavaria, Germany, known as one of the country’s oldest wine-growing communities.
-
B.
Herrenberg
Herrenberg is a historic town in the German state of Baden-Württemberg, known for its well-preserved medieval center and proximity to the Schönbuch Nature Park.
-
C.
Gerlachsheim
Gerlachsheim is a district of the town Lauda-Königshofen in the Main-Tauber-Kreis region of Baden-Württemberg, Germany.
-
D.
Greifenburg
Greifenburg is a small market town in the Austrian state of Carinthia, known for its alpine setting and popularity as a paragliding and outdoor recreation destination.
-
E.
Schwabhausen
Schwabhausen is a municipality in Bavaria, Germany, known for its rural character and location within the greater Munich metropolitan region.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b51cd5cc81909ac1187971e8a8ad |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e8a854e8ec81909efd41c1e959cc61 |
completed | April 22, 2026, 10:52 a.m. |
Created at: April 16, 2026, 4:54 p.m.