Triple

T19539098
Position Surface form Disambiguated ID Type / Status
Subject Maulbronn E488846 entity
Predicate locatedNear P294 FINISHED
Object Pforzheim 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: Pforzheim | Statement: [Maulbronn, locatedNear, Pforzheim]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Pforzheim
Context triple: [Maulbronn, locatedNear, Pforzheim]
  • A. Pforzheim chosen
    Pforzheim is a city in southwestern Germany, historically known for its jewelry and watchmaking industry and its heavy destruction during World War II.
  • B. Rastatt
    Rastatt is a historic town in southwestern Germany, known for its Baroque architecture and its role as the site of significant early 18th-century peace negotiations.
  • C. Rottweil
    Rottweil is a historic town in southwestern Germany known for its medieval architecture and as the namesake of the Rottweiler dog breed.
  • D. Tuttlingen
    Tuttlingen is a town in the state of Baden-Württemberg in southern Germany, known as a major center of the medical technology and surgical instrument industry.
  • E. Ittlingen
    Ittlingen is a small municipality in the German state of Baden-Württemberg, located within the Heilbronn region.
  • 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_69d8e8db5b6c8190984b61f91981f575 completed April 10, 2026, 12:11 p.m.
NER Named-entity recognition batch_69e638710b8c81908335535869fc9130 completed April 20, 2026, 2:30 p.m.
Created at: April 10, 2026, 1:41 p.m.