Triple

T10283977
Position Surface form Disambiguated ID Type / Status
Subject Overijse E241178 entity
Predicate hasSubMunicipality P747 FINISHED
Object Overijse proper E241178 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: Overijse proper | Statement: [Overijse, hasSubMunicipality, Overijse proper]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Overijse proper
Context triple: [Overijse, hasSubMunicipality, Overijse proper]
  • A. Overijse chosen
    Overijse is a municipality in the Flemish Brabant province of Belgium, known for its green residential character and extensive vineyards.
  • B. Bollenstreek
    Bollenstreek is a coastal region in the western Netherlands famous for its extensive flower bulb fields and springtime tulip displays.
  • C. Overbetuwe
    Overbetuwe is a municipality in the Dutch province of Gelderland, located in the Betuwe region and known for its rural landscape and fruit cultivation.
  • D. Oosterwijtwerd
    Oosterwijtwerd is a small village in the province of Groningen in the northern Netherlands, known for its rural character and historic church.
  • E. Zijdelwaard
    Zijdelwaard is a residential neighborhood in the town of Uithoorn in the province of North Holland, Netherlands.
  • 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_69d381aaafc08190af475ef58dc16aba completed April 6, 2026, 9:49 a.m.
NER Named-entity recognition batch_69d4d2b5853081909cd0397e08a0f44d completed April 7, 2026, 9:47 a.m.
NED1 Entity disambiguation (via context triple) batch_69d6f83c3c488190b728783bc260b006 completed April 9, 2026, 12:52 a.m.
Created at: April 6, 2026, 11:39 a.m.