Triple

T4740766
Position Surface form Disambiguated ID Type / Status
Subject Battle of Lutterberg (1762) E105233 entity
Predicate namedAfter P63 FINISHED
Object Lutterberg E409660 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: Lutterberg | Statement: [Battle of Lutterberg (1762), namedAfter, Lutterberg]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lutterberg
Context triple: [Battle of Lutterberg (1762), namedAfter, Lutterberg]
  • A. Lutterberg chosen
    Lutterberg is a village in Lower Saxony, Germany, historically notable as the site of the 1758 Battle of Lutterberg during the Seven Years' War.
  • B. Hesselberg
    Hesselberg is a prominent hill in Bavaria, Germany, known as the highest elevation of the Franconian Alb region.
  • C. Valkhof
    Valkhof is a historic site in Nijmegen, Netherlands, known for its hilltop park and medieval castle ruins overlooking the River Waal.
  • D. Steigerwald
    Steigerwald is a forested hill range and nature area in northern Bavaria, Germany, known for its beech forests, vineyards, and traditional Franconian landscapes.
  • E. Trautenstein
    Trautenstein is a village in the Harz region of Saxony-Anhalt, Germany, now incorporated into the town of Oberharz am Brocken.
  • 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_69bd43ef87a48190a5bc3600711aa032 completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd64a5f3548190a6acf1dcfd64d11d completed March 20, 2026, 3:15 p.m.
NED1 Entity disambiguation (via context triple) batch_69be3a211d2c8190a87ad81ef90dcf3b completed March 21, 2026, 6:26 a.m.
Created at: March 20, 2026, 1:19 p.m.