Triple

T16805151
Position Surface form Disambiguated ID Type / Status
Subject Ubbergen E408461 entity
Predicate hasCapital P204 FINISHED
Object Beek-Ubbergen E408450 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: Beek-Ubbergen | Statement: [Ubbergen, hasCapital, Beek-Ubbergen]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Beek-Ubbergen
Context triple: [Ubbergen, hasCapital, Beek-Ubbergen]
  • A. Beek-Ubbergen chosen
    Beek-Ubbergen is a village in the Dutch province of Gelderland, known for its scenic hilly landscape near Nijmegen and close to the German border.
  • B. Woudwetering
    Woudwetering is a Dutch waterway in South Holland that serves as an important local canal near the village of Woubrugge.
  • C. Bodegraven
    Bodegraven is a town in the Dutch province of South Holland, known for its cheese production and location in the Green Heart region of the Netherlands.
  • D. Uithoorn
    Uithoorn is a town and municipality in the province of North Holland in the Netherlands, situated along the Amstel River.
  • E. Vollenhove
    Vollenhove is a historic town in the Dutch province of Overijssel, known for its former status as a regional administrative and noble center with several notable estates and churches.
  • 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_69d88393905081908d00a86b99996ac8 completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e3b2cb68508190a05749bad68f7b43 completed April 18, 2026, 4:35 p.m.
NED1 Entity disambiguation (via context triple) batch_6a00bb0dce448190b20ca3d60d9fc475 completed May 10, 2026, 5:06 p.m.
Created at: April 10, 2026, 5:22 a.m.