Triple

T13414872
Position Surface form Disambiguated ID Type / Status
Subject Grünau E313185 entity
Predicate adjacentTo P224 FINISHED
Object Bohnsdorf E688751 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: Bohnsdorf | Statement: [Grünau, adjacentTo, Bohnsdorf]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bohnsdorf
Context triple: [Grünau, adjacentTo, Bohnsdorf]
  • A. Bohnsdorf chosen
    Bohnsdorf is a residential locality in the southeastern part of Berlin, Germany, known for its suburban character and proximity to the city’s green and lake-rich areas.
  • B. Biendorf
    Biendorf is a small municipality in northern Germany notable as the birthplace of German Field Marshal Helmuth von Moltke the Younger.
  • C. Heinersdorf
    Heinersdorf is a residential locality in the borough of Pankow in Berlin, Germany, known for its suburban character and proximity to the city center.
  • D. Hubersdorf
    Hubersdorf is a small municipality located in the canton of Solothurn in northwestern Switzerland.
  • E. Burkhardtsdorf
    Burkhardtsdorf is a small municipality in the Erzgebirge (Ore Mountains) region of Saxony, eastern Germany.
  • 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_69d806ad0c44819088833ae1ec9e9690 completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69dbaeb6e904819098cc9153fd2feaf5 completed April 12, 2026, 2:39 p.m.
NED1 Entity disambiguation (via context triple) batch_69fe8bba60c8819087b614cea03eb078 completed May 9, 2026, 1:19 a.m.
Created at: April 9, 2026, 9:39 p.m.