Triple

T22615830
Position Surface form Disambiguated ID Type / Status
Subject municipality of Heusden E558142 entity
Predicate contains P35 FINISHED
Object Heesbeen 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: Heesbeen | Statement: [municipality of Heusden, contains, Heesbeen]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Heesbeen
Context triple: [municipality of Heusden, contains, Heesbeen]
  • A. Heesbeen chosen
    Heesbeen is a small village in the Dutch province of North Brabant, historically part of the Land van Heusden region.
  • B. Beckeln
    Beckeln is a small municipality in Lower Saxony, Germany, known for its rural character and agricultural surroundings.
  • C. Denmead
    Denmead is a large village and civil parish in Hampshire, England, situated near Waterlooville and on the edge of the South Downs.
  • D. Burdaard
    Burdaard is a small village in the Dutch province of Friesland, known for its traditional windmill and location along the Dokkumer Ee canal.
  • E. Hannut
    Hannut is a municipality in the French-speaking Walloon Region of Belgium, known for its rural character and location between Liège and Brussels.
  • 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.