Triple

T4367752
Position Surface form Disambiguated ID Type / Status
Subject Duchy of Saxe-Eisenach E98818 entity
Predicate capital P234 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: [Duchy of Saxe-Eisenach, capital, Eisenach]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Eisenach
Context triple: [Duchy of Saxe-Eisenach, capital, 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. Kronach
    Kronach is a historic town in northern Bavaria, Germany, known for its well-preserved medieval old town and the imposing Rosenberg Fortress.
  • C. 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.
  • D. Mühlhausen
    Mühlhausen is a historic town in central Germany, known for its well-preserved medieval architecture and cultural heritage.
  • E. Schmalkalden
    Schmalkalden is a historic town in the German state of Thuringia, known for its well-preserved medieval architecture and role in Reformation-era politics.
  • 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_69b3454db3708190aeafd814413c4c3d completed March 12, 2026, 10:59 p.m.
NER Named-entity recognition batch_69b35201be7081908808e81634060f95 completed March 12, 2026, 11:53 p.m.
NED1 Entity disambiguation (via context triple) batch_69bd4216d3f48190a614f61b2e10f794 completed March 20, 2026, 12:48 p.m.
Created at: March 12, 2026, 11:17 p.m.