Triple

T12989097
Position Surface form Disambiguated ID Type / Status
Subject Doetinchem E321848 entity
Predicate twinTown P1072 FINISHED
Object Raesfeld E610412 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: Raesfeld | Statement: [Doetinchem, twinTown, Raesfeld]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Raesfeld
Context triple: [Doetinchem, twinTown, Raesfeld]
  • A. Raesfeld chosen
    Raesfeld is a municipality in western Germany’s North Rhine-Westphalia, known for its historic moated castle and rural surroundings.
  • B. Lülsfeld
    Lülsfeld is a small municipality in the Schweinfurt district of Lower Franconia in northern Bavaria, Germany.
  • C. Birkenfeld
    Birkenfeld is a town in western Germany historically associated with the Palatine counts, including Christian I of Birkenfeld-Zweibrücken.
  • D. Erstfeld
    Erstfeld is a municipality in the Swiss canton of Uri, situated in a mountainous valley that serves as an important transport corridor through the Alps.
  • E. Wilhelmsruh
    Wilhelmsruh is a locality in the borough of Pankow in Berlin, Germany, known for its residential character and historical ties to Berlin’s former border zone.
  • 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_69d8076479b8819090afce3591939cdf completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69d97e75b9f88190a54372c2a1223a4e completed April 10, 2026, 10:49 p.m.
NED1 Entity disambiguation (via context triple) batch_69fdfb6b97888190923ce7a6e59ff752 completed May 8, 2026, 3:04 p.m.
Created at: April 9, 2026, 8:42 p.m.