Triple

T13684174
Position Surface form Disambiguated ID Type / Status
Subject Woudenberg E328078 entity
Predicate sharesBorderWith P224 FINISHED
Object Scherpenzeel E421484 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: Scherpenzeel | Statement: [Woudenberg, sharesBorderWith, Scherpenzeel]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Scherpenzeel
Context triple: [Woudenberg, sharesBorderWith, Scherpenzeel]
  • A. Scherpenzeel chosen
    Scherpenzeel is a small Dutch municipality in the province of Gelderland, known for its rural character and historic village center.
  • B. Heezen
    Heezen is a surname most notably associated with American geologist and oceanographer Bruce C. Heezen, a pioneer in mapping the ocean floor.
  • C. Landsmeer
    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.
  • D. Zwanenburg
    Zwanenburg is a village in North Holland, Netherlands, situated near Amsterdam and known as a suburban residential community within the Haarlemmermeer municipality.
  • E. Ruurlo
    Ruurlo is a village in the Dutch province of Gelderland, known for its historic estates and rural character.
  • 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_69d8076f1fa8819094664a59b55010df completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69dbc66f8acc8190b2a82b722930b995 completed April 12, 2026, 4:21 p.m.
NED1 Entity disambiguation (via context triple) batch_69f7b063661481908da569084c20f37c completed May 3, 2026, 8:30 p.m.
Created at: April 9, 2026, 9:53 p.m.