Triple

T20857723
Position Surface form Disambiguated ID Type / Status
Subject Heeze-Leende E513523 entity
Predicate contains P35 FINISHED
Object Leenderbos 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: Leenderbos | Statement: [Heeze-Leende, contains, Leenderbos]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Leenderbos
Context triple: [Heeze-Leende, contains, Leenderbos]
  • A. Leenderbos chosen
    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.
  • B. 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.
  • C. Zandbergen
    Zandbergen is a small hamlet in the municipality of Losser in the province of Overijssel in the eastern Netherlands.
  • D. Zandbergen
    Zandbergen is a village in East Flanders, Belgium, that forms part of the municipality of Geraardsbergen.
  • E. Ternaard
    Ternaard is a small village in the Dutch province of Friesland, known for its rural character and location near the Wadden Sea.
  • 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_69e0b4f5b01081909452f654d2fc3f50 completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6c3a9fd7881908ae4c5c63f64efc0 completed April 21, 2026, 12:24 a.m.
Created at: April 16, 2026, 12:44 p.m.