Triple
T13539057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eisenach–Lichtenfels railway |
E323334
|
entity |
| Predicate | endPoint |
P390
|
FINISHED |
| Object | Lichtenfels |
E11679
|
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: Lichtenfels | Statement: [Eisenach–Lichtenfels railway, endPoint, Lichtenfels]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lichtenfels Context triple: [Eisenach–Lichtenfels railway, endPoint, Lichtenfels]
-
A.
Lichtenfels
chosen
Lichtenfels is a town in the Upper Franconia region of Bavaria, Germany, known for its basket-making tradition and historic architecture.
-
B.
Lichtenfels
Lichtenfels is a small town in the Waldeck-Frankenberg district of northern Hesse, Germany, known for its rural setting and proximity to the Edersee and Kellerwald-Edersee National Park.
-
C.
Lülsfeld
Lülsfeld is a small municipality in the Schweinfurt district of Lower Franconia in northern Bavaria, Germany.
-
D.
Altenstadt
Altenstadt is a small Bavarian municipality in southern Germany, situated within the rural district of Weilheim-Schongau.
-
E.
Lauterhofen
Lauterhofen is a market town in Bavaria, Germany, known for its rural character and location within the Upper Palatinate region.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d8076776248190bdf0d4fa1f85a5fc |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbafd7ad9481908fe1d7ffcf8fab71 |
completed | April 12, 2026, 2:44 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f75d7cfe24819096e8f4cd496a6fd7 |
completed | May 3, 2026, 2:36 p.m. |
Created at: April 9, 2026, 9:45 p.m.