Triple

T15423788
Position Surface form Disambiguated ID Type / Status
Subject Schwelm E369451 entity
Predicate locatedNear P294 FINISHED
Object Gevelsberg E566784 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: Gevelsberg | Statement: [Schwelm, locatedNear, Gevelsberg]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Gevelsberg
Context triple: [Schwelm, locatedNear, Gevelsberg]
  • A. Gevelsberg chosen
    Gevelsberg is a town in North Rhine-Westphalia, Germany, situated in the Ennepe-Ruhr district within the Ruhr metropolitan region.
  • B. Werdohl
    Werdohl is a town in the Märkischer Kreis district of North Rhine-Westphalia, Germany, known for its metalworking industry and location in the hilly Sauerland region.
  • C. Gescher
    Gescher is a small town in western Germany’s Münsterland region, noted for its traditional bell foundries and rural character.
  • D. Fritzlar
    Fritzlar is a historic town in northern Hesse, Germany, known for its well-preserved medieval old town and its significance in early German Christian history.
  • E. 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.
  • 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_69d85a1849f48190bf898068b2806fae completed April 10, 2026, 2:02 a.m.
NER Named-entity recognition batch_69e03ec032548190840b558dde6057c7 completed April 16, 2026, 1:43 a.m.
NED1 Entity disambiguation (via context triple) batch_6a001799fbac8190b75a48a8c63e3381 completed May 10, 2026, 5:28 a.m.
Created at: April 10, 2026, 3:20 a.m.