Triple

T22564823
Position Surface form Disambiguated ID Type / Status
Subject Gasselte E557918 entity
Predicate locatedNear P294 FINISHED
Object Gieten 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: Gieten | Statement: [Gasselte, locatedNear, Gieten]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Gieten
Context triple: [Gasselte, locatedNear, Gieten]
  • A. Gieten chosen
    Gieten is a village in the Dutch province of Drenthe that serves as the main administrative and service hub for the surrounding rural municipality.
  • B. Everdingen
    Everdingen is a village in the Dutch province of Utrecht, known for its rural character and historic fortifications along the Lek River.
  • C. Geldern
    Geldern is a historic town in western Germany, notable as the namesake and former center of the medieval Duchy of Guelders.
  • D. 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.
  • E. Tienhoven
    Tienhoven is a small village in the Dutch province of Utrecht, known for its rural landscape and location within the municipality of Stichtse Vecht.
  • 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_69e11e5ae4ac8190b1f503457603d969 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f15fa8d8388190856198547d56dce6 completed April 29, 2026, 1:32 a.m.
Created at: April 16, 2026, 8:52 p.m.