Triple

T3694264
Position Surface form Disambiguated ID Type / Status
Subject Beinsdorp E78416 entity
Predicate hasRoadConnectionTo P11435 FINISHED
Object Hillegom E209080 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: Hillegom | Statement: [Beinsdorp, hasRoadConnectionTo, Hillegom]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hillegom
Context triple: [Beinsdorp, hasRoadConnectionTo, Hillegom]
  • A. Hillegom chosen
    Hillegom is a town in the western Netherlands known for its flower bulb cultivation and location within the historic Duin- en Bollenstreek (Dune and Bulb Region).
  • B. Hulst
    Hulst is a historic fortified town and municipality in the Dutch province of Zeeland, near the border with Belgium.
  • C. Valkenswaard
    Valkenswaard is a town in the southern Netherlands known for its strong equestrian culture and international show jumping events.
  • D. Zaltbommel
    Zaltbommel is a historic Dutch town in the province of Gelderland, known for its medieval center and strategic location along the River Waal.
  • E. Hoeksche Waard
    Hoeksche Waard is a rural island and municipality in South Holland, Netherlands, known for its agricultural landscape and small towns.
  • 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_69ad85e3b1888190abc983e06968696d completed March 8, 2026, 2:21 p.m.
NER Named-entity recognition batch_69adc4e9e4748190aa178692ef27e3a6 completed March 8, 2026, 6:50 p.m.
NED1 Entity disambiguation (via context triple) batch_69c7bf5fcf588190bcd52c539c3958b0 completed March 28, 2026, 11:45 a.m.
Created at: March 8, 2026, 3:26 p.m.