Triple

T14868007
Position Surface form Disambiguated ID Type / Status
Subject Wettingen E349667 entity
Predicate locatedNear P294 FINISHED
Object Baden E945291 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: [Wettingen, locatedNear, Baden]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Baden
Context triple: [Wettingen, locatedNear, 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 was a historical state in southwestern Germany that existed as a grand duchy before being incorporated into the German Empire.
  • C. Baden
    Baden is a district or locality within the German town of Achim, situated in the state of Lower Saxony.
  • D. 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.
  • E. Baden District chosen
    Baden District is an administrative district in northern Switzerland known for its historic spa town of Baden and its role as a regional economic and transportation hub within the Canton of Aargau.
  • 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_69d822ee4f408190b6ac3b2fa434f0df completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69ded5776b848190bfe3a06ff261dc31 completed April 15, 2026, 12:01 a.m.
NED1 Entity disambiguation (via context triple) batch_69fe6b5101a48190937a86b6eda79c55 completed May 8, 2026, 11:01 p.m.
Created at: April 10, 2026, 1:55 a.m.