Triple

T13113879
Position Surface form Disambiguated ID Type / Status
Subject Joachimsthal E311042 entity
Predicate locatedInRegion P40 FINISHED
Object Schorfheide E316727 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: Schorfheide | Statement: [Joachimsthal, locatedInRegion, Schorfheide]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Schorfheide
Context triple: [Joachimsthal, locatedInRegion, Schorfheide]
  • A. Schorfheide chosen
    Schorfheide is a large forested and lake-rich area in Brandenburg, Germany, known for its protected natural landscapes and historical use as a royal and political hunting ground.
  • B. Schönewalde
    Schönewalde is a town in the state of Brandenburg, Germany, known for hosting a German Air Force base.
  • C. Stolzenhagen
    Stolzenhagen is a village and locality within the municipality of Wandlitz in the state of Brandenburg, Germany.
  • D. Schönwalde
    Schönwalde is a locality within the municipality of Wandlitz in the state of Brandenburg, Germany.
  • E. Blankenfelde-Mahlow
    Blankenfelde-Mahlow is a municipality in the Teltow-Fläming district of Brandenburg, Germany, located just south of Berlin and known as a suburban residential area within the Berlin metropolitan region.
  • 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_69d806a872d08190a329806f8ff30df4 completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69d9817f8ee8819084078b4bec5e4f18 completed April 10, 2026, 11:02 p.m.
NED1 Entity disambiguation (via context triple) batch_69f77f7696f0819094825b158e1e9a8c completed May 3, 2026, 5:01 p.m.
Created at: April 9, 2026, 9:06 p.m.