Triple
T8375488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Germany |
E197565
|
entity |
| Predicate | containsCity |
P294
|
FINISHED |
| Object | Eisenach |
E153084
|
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: Eisenach | Statement: [Central Germany, containsCity, Eisenach]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Eisenach Context triple: [Central Germany, containsCity, Eisenach]
-
A.
Eisenach
chosen
Eisenach is a historic town in central Germany best known for its associations with Martin Luther and as the birthplace of composer Johann Sebastian Bach.
-
B.
Rudolstadt
Rudolstadt is a historic town in the German state of Thuringia, known for its picturesque old town, Heidecksburg Castle, and cultural festivals.
-
C.
Kronach
Kronach is a historic town in northern Bavaria, Germany, known for its well-preserved medieval old town and the imposing Rosenberg Fortress.
-
D.
Gotha
Gotha is a historic German city in Thuringia known for its former ducal court, cultural heritage, and role as a residence of various German noble houses.
-
E.
Mühlhausen
Mühlhausen is a historic town in central Germany, known for its well-preserved medieval architecture and cultural heritage.
- 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_69ca82f56730819080cec5d991c76f4c |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb80bf6b8081909b98762b1f900bef |
completed | March 31, 2026, 8:07 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cf5127db38819087d5ba71b6064998 |
completed | April 3, 2026, 5:33 a.m. |
Created at: March 30, 2026, 6:01 p.m.