Triple

T8797350
Position Surface form Disambiguated ID Type / Status
Subject Oberursel (Taunus) E209321 entity
Predicate borderedBy P224 FINISHED
Object Friedrichsdorf E263386 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: Friedrichsdorf | Statement: [Oberursel (Taunus), borderedBy, Friedrichsdorf]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Friedrichsdorf
Context triple: [Oberursel (Taunus), borderedBy, Friedrichsdorf]
  • A. Friedrichsdorf chosen
    Friedrichsdorf is a town in the German state of Hesse, located north of Frankfurt and known historically for its Huguenot heritage and proximity to the Taunus mountains.
  • B. Degendorf
    Degendorf is a locality within the Bavarian town and district of Lichtenfels in Germany.
  • C. Ruppersdorf
    Ruppersdorf is a small locality in Germany, historically part of East Prussia, known as the birthplace of German general Otto Lasch.
  • D. Rahnsdorf
    Rahnsdorf is a lakeside locality in eastern Berlin, Germany, known for its village-like character, forests, and waterfront along the Müggelsee and nearby waterways.
  • E. Hennigsdorf
    Hennigsdorf is a town in the German state of Brandenburg, located just northwest of Berlin and known for its industrial heritage and proximity to the Havel River.
  • 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_69ca836240888190a62b262e56a69d2f completed March 30, 2026, 2:06 p.m.
NER Named-entity recognition batch_69cc5fa370d08190885ef65e3a3e56d3 completed March 31, 2026, 11:58 p.m.
NED1 Entity disambiguation (via context triple) batch_69d017060fd08190bd053f988bd74048 completed April 3, 2026, 7:37 p.m.
Created at: March 30, 2026, 6:44 p.m.