Triple

T9413973
Position Surface form Disambiguated ID Type / Status
Subject district of Rosenheim E226767 entity
Predicate contains P35 FINISHED
Object Kolbermoor E141634 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: Kolbermoor | Statement: [district of Rosenheim, contains, Kolbermoor]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kolbermoor
Context triple: [district of Rosenheim, contains, Kolbermoor]
  • A. Kolbermoor chosen
    Kolbermoor is a small Bavarian town in southern Germany, known as the birthplace of footballer Bastian Schweinsteiger.
  • B. Seebruck
    Seebruck is a Bavarian lakeside village and popular holiday resort on the northern shore of Lake Chiemsee in southern Germany.
  • C. Landensberg
    Landensberg is a small municipality in the Bavarian region of southern Germany.
  • D. Lochau
    Lochau is a locality in Germany historically noted as the place where the influential Reformation-era prince Frederick the Wise died.
  • E. Bürmoos
    Bürmoos is a small Austrian municipality located in the state of Salzburg, known for its residential character and proximity to the city of Salzburg.
  • 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_69ca843280488190bc65600e843ef9e6 completed March 30, 2026, 2:09 p.m.
NER Named-entity recognition batch_69cd68c680e48190be82e3829e8711f0 completed April 1, 2026, 6:49 p.m.
NED1 Entity disambiguation (via context triple) batch_69d107b63cf48190a072e3434a7b85a8 completed April 4, 2026, 12:44 p.m.
Created at: March 30, 2026, 7:47 p.m.