Triple

T22154054
Position Surface form Disambiguated ID Type / Status
Subject Montferland E547486 entity
Predicate hasBorderWith P224 FINISHED
Object Zevenaar 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: Zevenaar | Statement: [Montferland, hasBorderWith, Zevenaar]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Zevenaar
Context triple: [Montferland, hasBorderWith, Zevenaar]
  • A. Zevenaar chosen
    Zevenaar is a town and municipality in the eastern Netherlands, near the German border in the province of Gelderland.
  • B. Achtmaal
    Achtmaal is a small village in the municipality of Zundert in the Dutch province of North Brabant.
  • C. De Molenaar
    De Molenaar is a Dutch surname, typically meaning “the miller,” associated with individuals or families historically linked to milling.
  • D. Neerwinden
    Neerwinden is a village in present-day Belgium known primarily as the site of two major 18th-century battles during the War of the Austrian Succession and the French Revolutionary Wars.
  • E. Vriezekoop
    Vriezekoop is a small village in the Dutch province of South Holland, known for its rural character and location along the Westeinderplassen near Leimuiden.
  • 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.