Triple

T4005853
Position Surface form Disambiguated ID Type / Status
Subject Dutch Low Saxon E89523 entity
Predicate hasDialect P4251 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: [Dutch Low Saxon, hasDialect, Stellingwerfs]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Stellingwerfs
Context triple: [Dutch Low Saxon, hasDialect, 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. Voorburg
    Voorburg is a historic town in the Netherlands, now part of the municipality of Leidschendam-Voorburg, known for its rich cultural heritage and proximity to The Hague.
  • E. Hellevoetsluis
    Hellevoetsluis is a historic Dutch port town known for its maritime heritage and coastal location in the western 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_69aed9585e788190bec2d39deba3750f completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69aefa60c500819084fcba785b2bf801 completed March 9, 2026, 4:50 p.m.
NED1 Entity disambiguation (via context triple) batch_69b54c648d3c8190a85e5cdfb20f6044 completed March 14, 2026, 11:54 a.m.
Created at: March 9, 2026, 3:34 p.m.