Triple

T19388311
Position Surface form Disambiguated ID Type / Status
Subject Purmerend E484991 entity
Predicate borderedBy P224 FINISHED
Object Landsmeer 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: Landsmeer | Statement: [Purmerend, borderedBy, Landsmeer]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Landsmeer
Context triple: [Purmerend, borderedBy, Landsmeer]
  • A. Landsmeer chosen
    Landsmeer is a small Dutch town and municipality in North Holland, situated just north of Amsterdam and known for its watery landscapes and nature reserves.
  • B. Leenderbos
    Leenderbos is a large forest and nature reserve in the Dutch province of North Brabant, known for its pine woods, heathlands, and walking and cycling trails.
  • C. Maasland
    Maasland is a historical region in the Low Countries centered along the river Meuse, known for its medieval political and cultural significance.
  • D. Zoutelande
    Zoutelande is a coastal village and popular seaside resort in the Dutch province of Zeeland, known for its beaches and dunes along the North Sea.
  • E. Scherpenzeel
    Scherpenzeel is a small Dutch municipality in the province of Gelderland, known for its rural character and historic village center.
  • 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_69d8e8d460d88190abf0591c5c9d2b0c completed April 10, 2026, 12:11 p.m.
NER Named-entity recognition batch_69e61b425e848190ab5ae8ae0a034fe2 completed April 20, 2026, 12:25 p.m.
Created at: April 10, 2026, 1:36 p.m.