Triple

T15596700
Position Surface form Disambiguated ID Type / Status
Subject Bramsche E374909 entity
Predicate hasSubdivision P747 FINISHED
Object Kalkriese E803539 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: Kalkriese | Statement: [Bramsche, hasSubdivision, Kalkriese]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kalkriese
Context triple: [Bramsche, hasSubdivision, Kalkriese]
  • A. Kalkriese chosen
    Kalkriese is a significant archaeological site in northwestern Germany, widely regarded as the likely location of the Battle of the Teutoburg Forest where Roman legions suffered a major defeat in 9 AD.
  • B. Kronshagen
    Kronshagen is a small municipality in the German state of Schleswig-Holstein, located near the city of Kiel.
  • C. Schildwolde
    Schildwolde is a village in the Dutch province of Groningen, known for its historic church and rural character within the municipality of Midden-Groningen.
  • D. Saerbeck
    Saerbeck is a municipality in North Rhine-Westphalia, Germany, known for its pioneering role in renewable energy and climate protection initiatives.
  • E. Rhauderfehn
    Rhauderfehn is a municipality in the East Frisian region of Lower Saxony in northwestern Germany, known for its origins as a peat colony and its characteristic canal landscape.
  • 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_69d85cce25008190b13b52745fbd719b completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69e04e5f9db8819083abf80f01f32b3d completed April 16, 2026, 2:50 a.m.
NED1 Entity disambiguation (via context triple) batch_69ff56ca72ec8190a237db843dc6d625 completed May 9, 2026, 3:46 p.m.
Created at: April 10, 2026, 4:12 a.m.