Triple

T1992558
Position Surface form Disambiguated ID Type / Status
Subject Weser Uplands E43282 entity
Predicate contains P35 FINISHED
Object Hamelin E178114 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: Hamelin | Statement: [Weser Uplands, contains, Hamelin]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hamelin
Context triple: [Weser Uplands, contains, Hamelin]
  • A. Hameln chosen
    Hameln is a historic town in Lower Saxony, Germany, best known as the setting of the Pied Piper of Hamelin legend.
  • B. Mouseton
    Mouseton is the fictional town that serves as the primary home and community setting for Mickey Mouse and many of his friends in Disney stories.
  • C. Hintonburg
    Hintonburg is a historic, arts-oriented urban neighbourhood in west-central Ottawa, known for its mix of residential streets, independent shops, and cultural venues.
  • D. Bremen-Verden
    Bremen-Verden was a former duchy in northern Germany that emerged from the secularized prince-bishoprics of Bremen and Verden and was at times ruled in personal union by Sweden.
  • E. Roxeter
    Roxeter is a historic settlement in Shropshire, England, known for its Roman origins and archaeological significance.
  • 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_69a88714cf2c819081644be450b8356e completed March 4, 2026, 7:25 p.m.
NER Named-entity recognition batch_69abb86275c88190bed869e9d3cf7ed5 completed March 7, 2026, 5:32 a.m.
NED1 Entity disambiguation (via context triple) batch_69ae033a39d48190b6389e22de0d4418 completed March 8, 2026, 11:16 p.m.
Created at: March 4, 2026, 7:37 p.m.