Triple

T22154058
Position Surface form Disambiguated ID Type / Status
Subject Montferland E547486 entity
Predicate hasBorderWith P224 FINISHED
Object Elten 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: Elten | Statement: [Montferland, hasBorderWith, Elten]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Elten
Context triple: [Montferland, hasBorderWith, Elten]
  • A. Elten chosen
    Elten is a historic village in western Germany near the Dutch border, known for its medieval heritage and the former Imperial Abbey that once dominated the area.
  • B. Elsene
    Elsene is a vibrant, multicultural municipality of Brussels in Belgium, known for its universities, art scene, and lively urban neighborhoods.
  • C. Velten
    Velten is a small town in the German state of Brandenburg, known historically for its stove and ceramics industry and its location just northwest of Berlin.
  • D. Heerdt
    Heerdt is a district of Düsseldorf, Germany, located on the left bank of the Rhine and characterized by a mix of residential, commercial, and industrial areas.
  • E. Ternaard
    Ternaard is a small village in the Dutch province of Friesland, known for its rural character and location near the Wadden Sea.
  • 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_69e11e3b52088190ad5df386d01eb2fb completed April 16, 2026, 5:36 p.m.
NER Named-entity recognition batch_69f129f6d5b88190badee2e515a3b633 completed April 28, 2026, 9:43 p.m.
Created at: April 16, 2026, 8:33 p.m.