Triple

T15812538
Position Surface form Disambiguated ID Type / Status
Subject Flemish Ardennes E383389 entity
Predicate contains P35 FINISHED
Object Kluisbergen E747367 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: Kluisbergen | Statement: [Flemish Ardennes, contains, Kluisbergen]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kluisbergen
Context triple: [Flemish Ardennes, contains, Kluisbergen]
  • A. Kluisbergen chosen
    Kluisbergen is a municipality in the Belgian province of East Flanders, known for its scenic hilly landscapes and cycling routes in the Flemish Ardennes.
  • B. Rijsbergen
    Rijsbergen is a village in the Dutch province of North Brabant, located near the Belgian border and known for its rural character.
  • C. Bergeijk
    Bergeijk is a municipality and village in the southern Netherlands, located in the province of North Brabant near the Belgian border.
  • D. Haaksbergen
    Haaksbergen is a town in the eastern Netherlands, near the German border, known for its rural surroundings and cross-border ties with neighboring German communities.
  • E. Grijpskerke
    Grijpskerke is a village in the Dutch province of Zeeland, located on the former island of Walcheren.
  • 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_69d86da2858c819090cc8481e7207b6e completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e0c4a069bc8190bf9504dc6c998fa2 completed April 16, 2026, 11:14 a.m.
NED1 Entity disambiguation (via context triple) batch_69ff9993c86c8190b1d106af7537080a completed May 9, 2026, 8:31 p.m.
Created at: April 10, 2026, 4:49 a.m.