Triple

T14401210
Position Surface form Disambiguated ID Type / Status
Subject Low Saxon dialect continuum E357073 entity
Predicate hasPart P35 FINISHED
Object Stellingwerfs E291122 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: Stellingwerfs | Statement: [Low Saxon dialect continuum, hasPart, Stellingwerfs]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Stellingwerfs
Context triple: [Low Saxon dialect continuum, hasPart, Stellingwerfs]
  • A. Weststellingwerf chosen
    Weststellingwerf is a municipality in the province of Friesland in the northern Netherlands, known for its rural landscape and small villages.
  • B. Brouwershaven
    Brouwershaven is a small historic town in the Dutch province of Zeeland, known for its maritime heritage and well-preserved old center.
  • C. Stellendam
    Stellendam is a small village in the western Netherlands, located on the island of Goeree-Overflakkee and known for its fishing harbor and proximity to the North Sea.
  • D. Onderdendam
    Onderdendam is a small historic village in the Dutch province of Groningen, known for its canals, bridges, and traditional architecture.
  • E. Nieuwendam
    Nieuwendam is a historic neighborhood in the northern part of Amsterdam, known for its former village character and waterfront location along the IJ.
  • 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_69d827927c988190ad98bb0360981783 completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de908500048190bb6a20fe318d5c62 completed April 14, 2026, 7:07 p.m.
NED1 Entity disambiguation (via context triple) batch_69fd5520c07c8190bfdaf224dd779ced completed May 8, 2026, 3:14 a.m.
Created at: April 10, 2026, 1:17 a.m.