Triple

T22207203
Position Surface form Disambiguated ID Type / Status
Subject Tervuren E548842 entity
Predicate nearbyCity P350 FINISHED
Object Overijse 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: Overijse | Statement: [Tervuren, nearbyCity, Overijse]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Overijse
Context triple: [Tervuren, nearbyCity, Overijse]
  • A. Overijse chosen
    Overijse is a municipality in the Flemish Brabant province of Belgium, known for its green residential character and extensive vineyards.
  • B. Waalre
    Waalre is a municipality and village in the southern Netherlands, located in the province of North Brabant near the city of Eindhoven.
  • C. Schoonebeek
    Schoonebeek is a village in the municipality of Coevorden in the province of Drenthe in the northeastern Netherlands, known historically for its oil fields.
  • D. Geervliet
    Geervliet is a small historic town in the western Netherlands, located in the province of South Holland.
  • E. Betuwe
    Betuwe is a fertile riverine region in the Dutch province of Gelderland, renowned for its extensive fruit orchards and scenic landscapes between the Rhine and Waal rivers.
  • 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_69e11e3f7e04819089806d81d5ac431e completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f12b2936a481909aa84c7983ed49ee completed April 28, 2026, 9:48 p.m.
Created at: April 16, 2026, 8:36 p.m.