Triple

T22615828
Position Surface form Disambiguated ID Type / Status
Subject municipality of Heusden E558142 entity
Predicate contains P35 FINISHED
Object Hedikhuizen 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: Hedikhuizen | Statement: [municipality of Heusden, contains, Hedikhuizen]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hedikhuizen
Context triple: [municipality of Heusden, contains, Hedikhuizen]
  • A. Hedikhuizen chosen
    Hedikhuizen is a small village in the Dutch province of North Brabant, known for its historic rural character and location near the River Maas.
  • B. Uithuizen
    Uithuizen is a village in the Dutch province of Groningen known for its historic Menkemaborg manor and role as an administrative and service center for the surrounding rural area.
  • C. Zandhuizen
    Zandhuizen is a small village in the municipality of Weststellingwerf in the province of Friesland in the northern Netherlands.
  • D. Hornhuizen
    Hornhuizen is a small village in the province of Groningen in the northern Netherlands, known for its rural landscape and historic church.
  • E. Harksheide
    Harksheide was a former municipality in Schleswig-Holstein, Germany, that later became part of the city of Norderstedt.
  • 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_69e24545a8e08190bfa7482a2c725ff1 completed April 17, 2026, 2:35 p.m.
NER Named-entity recognition batch_69f167edec2481909c2f06607b3cb8f6 completed April 29, 2026, 2:07 a.m.
Created at: April 17, 2026, 2:59 p.m.