Triple

T14644571
Position Surface form Disambiguated ID Type / Status
Subject Mecklenburgische Schweiz E343812 entity
Predicate hasSettlement P1068 FINISHED
Object Malchin E973954 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: Malchin | Statement: [Mecklenburgische Schweiz, hasSettlement, Malchin]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Malchin
Context triple: [Mecklenburgische Schweiz, hasSettlement, Malchin]
  • A. Malchin chosen
    Malchin is a small town in the Mecklenburgische Seenplatte district of Mecklenburg-Vorpommern in northern Germany.
  • B. Talbach
    Talbach is a small stream in Switzerland that serves as a tributary of the Ergolz River in the Basel-Landschaft region.
  • C. Zernien
    Zernien is a municipality in Lower Saxony, Germany, situated within the collective municipality (Samtgemeinde) of Elbtalaue.
  • D. Payerne
    Payerne is a historic town and municipality in the canton of Vaud, Switzerland, known for its medieval abbey and regional agricultural significance.
  • E. Zepernick
    Zepernick is a locality in the German state of Brandenburg that now forms part of the municipality of Panketal.
  • 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_69d822e1a2cc81908e5bb93cf61ce3cc completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69deb4ea6d8481908e6331ca173c646b completed April 14, 2026, 9:43 p.m.
NED1 Entity disambiguation (via context triple) batch_69fdd5d5d05481908dbb23392c05d23b completed May 8, 2026, 12:23 p.m.
Created at: April 10, 2026, 1:26 a.m.