Triple

T18264254
Position Surface form Disambiguated ID Type / Status
Subject Vechigen E437440 entity
Predicate hasLocality P7943 FINISHED
Object Radelfingen (Vechigen) NE NERFINISHED

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: Radelfingen (Vechigen) | Statement: [Vechigen, hasLocality, Radelfingen (Vechigen)]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Radelfingen (Vechigen)
Context triple: [Vechigen, hasLocality, Radelfingen (Vechigen)]
  • A. Radelfingen chosen
    Radelfingen is a rural municipality in the canton of Bern in Switzerland, known for its agricultural landscape and small-village character.
  • B. Andelfingen
    Andelfingen is a municipality and regional center in the canton of Zürich in northern Switzerland, known for its rural character and vineyards along the Thur River.
  • C. Weinfelden
    Weinfelden is a town and municipality in northeastern Switzerland that serves as an important regional center in the canton of Thurgau.
  • D. Röfingen
    Röfingen is a small municipality in the Bavarian region of Swabia in southern Germany.
  • E. Remchingen
    Remchingen is a municipality in the Enzkreis district of Baden-Württemberg, Germany, situated along the Pfinz river between Karlsruhe and Pforzheim.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8b913351c8190932b6a426de04b41 completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e4ff78b188819081da8e1d389c6c79 completed April 19, 2026, 4:14 p.m.
Created at: April 10, 2026, 10:34 a.m.