Triple

T20827164
Position Surface form Disambiguated ID Type / Status
Subject Brombachsee E512732 entity
Predicate locatedNear P294 FINISHED
Object Absberg NE NERFINISHED

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: Absberg | Statement: [Brombachsee, locatedNear, Absberg]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Absberg
Context triple: [Brombachsee, locatedNear, Absberg]
  • A. Absberg chosen
    Absberg is a small municipality in the Franconian Lake District of Bavaria, Germany, known for its scenic location near Lake Brombach.
  • B. Abrahamsberg
    Abrahamsberg is a residential district in western Stockholm, Sweden, known for its 1930s–1940s functionalist architecture and location within the Bromma borough.
  • C. Ausserberg
    Ausserberg is a small Swiss mountain village and municipality in the canton of Valais, known for its scenic alpine setting and traditional rural character.
  • D. Lossberg
    Lossberg is a German surname most notably associated with the military strategist Fritz von Lossberg of the Imperial German Army during World War I.
  • E. Abstatt
    Abstatt is a small municipality in the German state of Baden-Württemberg, situated in the Heilbronn region and known for its wine-growing surroundings.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0b4ce39108190a6e8e5df4f1c8dc5 completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6c2fe54608190a061274bf4316610 completed April 21, 2026, 12:21 a.m.
Created at: April 16, 2026, 12:42 p.m.