Triple

T17321092
Position Surface form Disambiguated ID Type / Status
Subject Evangelical Church in Baden E420560 entity
Predicate locatedIn P40 FINISHED
Object Baden E220958 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: Baden | Statement: [Evangelical Church in Baden, locatedIn, Baden]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Baden
Context triple: [Evangelical Church in Baden, locatedIn, Baden]
  • A. Baden
    Baden is a historic spa town in present-day Switzerland known for hosting the 1714 Treaty of Baden that helped conclude the War of the Spanish Succession.
  • B. Baden
    Baden is a district or locality within the German town of Achim, situated in the state of Lower Saxony.
  • C. Baden chosen
    Baden was a historical state in southwestern Germany that existed as a grand duchy before being incorporated into the German Empire.
  • D. Baden-Rodemachern
    Baden-Rodemachern was a small German margraviate and noble residence associated with a cadet branch of the House of Baden in the early modern period.
  • E. Baden-Durlach
    Baden-Durlach was a historical Protestant margraviate in southwestern Germany that played a notable role in the religious and political conflicts of the Holy Roman Empire.
  • 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_69d889d22b848190a4663d0b8f8f76e7 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e439cf5394819089bff5f8dc2e8241 completed April 19, 2026, 2:11 a.m.
NED1 Entity disambiguation (via context triple) batch_6a018c483e988190a481b4c487f79329 completed May 11, 2026, 7:59 a.m.
Created at: April 10, 2026, 5:43 a.m.