Triple

T9540586
Position Surface form Disambiguated ID Type / Status
Subject Straubing-Bogen E230145 entity
Predicate contains P35 FINISHED
Object Bogen E805380 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: Bogen | Statement: [Straubing-Bogen, contains, Bogen]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bogen
Context triple: [Straubing-Bogen, contains, Bogen]
  • A. Bogen chosen
    Bogen is a historic town in Lower Bavaria, Germany, situated on the Danube River and known for its medieval heritage and regional significance.
  • B. Spreebogen
    Spreebogen is a prominent riverside area in central Berlin known for its sweeping bend of the River Spree and its concentration of major government and cultural buildings.
  • C. Bigen
    Bigen is one of the small islands that make up Maloelap Atoll in the Marshall Islands, located in the central Pacific Ocean.
  • D. Lügde
    Lügde is a small historic town in North Rhine-Westphalia, Germany, known for its traditional Easter customs and scenic location near the Weser Uplands.
  • E. Bechtsrieth
    Bechtsrieth is a small municipality in the Upper Palatinate region of Bavaria, 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_69ca847b1b3081908f72bc932c17cc41 completed March 30, 2026, 2:11 p.m.
NER Named-entity recognition batch_69cd98e695948190ab107fff38c57de7 completed April 1, 2026, 10:15 p.m.
NED1 Entity disambiguation (via context triple) batch_69d15278efd4819091e707aabd9a59d7 completed April 4, 2026, 6:03 p.m.
Created at: March 30, 2026, 8:01 p.m.