Triple

T20885302
Position Surface form Disambiguated ID Type / Status
Subject Oldambt E514261 entity
Predicate contains P35 FINISHED
Object Nieuwolda 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: Nieuwolda | Statement: [Oldambt, contains, Nieuwolda]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Nieuwolda
Context triple: [Oldambt, contains, Nieuwolda]
  • A. Nieuwolda chosen
    Nieuwolda is a small village in the municipality of Oldambt in the province of Groningen in the northeastern Netherlands.
  • B. Veenendaal
    Veenendaal is a Dutch town and municipality in the central Netherlands, known for its location between Utrecht and the Veluwe and its mix of residential, commercial, and light industrial areas.
  • C. Stitswerd
    Stitswerd is a small village in the northern Netherlands, located in the province of Groningen.
  • D. Leusden
    Leusden is a Dutch town and municipality in the central Netherlands, known for its green residential character and proximity to the city of Amersfoort.
  • E. Oudelande
    Oudelande is a small village in the Dutch province of Zeeland, known for its rural character and traditional polder landscape.
  • 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_69e0b4f733f081908a401c0b7beb0b9f completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6c67c9d1c81908031eb77c124f119 completed April 21, 2026, 12:36 a.m.
Created at: April 16, 2026, 12:46 p.m.