Triple

T3790142
Position Surface form Disambiguated ID Type / Status
Subject Battle of Corbach E89624 entity
Predicate location P40 FINISHED
Object Corbach E289018 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: Corbach | Statement: [Battle of Corbach, location, Corbach]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Corbach
Context triple: [Battle of Corbach, location, Corbach]
  • A. Lemgo
    Lemgo is a historic town in the Lippe district of North Rhine-Westphalia, Germany, known for its well-preserved medieval architecture and Hanseatic heritage.
  • B. Radevormwald
    Radevormwald is a small historic town in North Rhine-Westphalia, western Germany, known for its hilly Bergisches Land landscape and traditional textile and metalworking industries.
  • C. Eberbach
    Eberbach is a small historic town in southwestern Germany, known for its picturesque location in the Odenwald hills along the Neckar River.
  • D. Korbach chosen
    Korbach is a historic town in the German state of Hesse, known as the district seat of Waldeck-Frankenberg and for its well-preserved medieval old town.
  • E. Rheydt
    Rheydt is a district of the German city of Mönchengladbach in North Rhine-Westphalia, historically an independent town in the Rhineland.
  • 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_69aed9597d6881909b6ee3b9de859223 completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69aee76733248190a24a1143c64bd6c6 completed March 9, 2026, 3:29 p.m.
NED1 Entity disambiguation (via context triple) batch_69b51c70a98081908e86293f7e684649 completed March 14, 2026, 8:29 a.m.
Created at: March 9, 2026, 3:15 p.m.