Triple

T17064388
Position Surface form Disambiguated ID Type / Status
Subject Sallaands E414044 entity
Predicate hasDialectContinuumWith P18451 FINISHED
Object Achterhoeks E14290 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: Achterhoeks | Statement: [Sallaands, hasDialectContinuumWith, Achterhoeks]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Achterhoeks
Context triple: [Sallaands, hasDialectContinuumWith, Achterhoeks]
  • A. Achterhooks chosen
    Achterhooks is a regional Low Saxon dialect spoken in the Achterhoek area of the eastern Netherlands.
  • B. Overhoeks
    Overhoeks is a modern waterfront district in Amsterdam known for its contemporary architecture, cultural venues, and redevelopment of former industrial land along the IJ river.
  • C. De Akkers
    De Akkers is a metro station in Spijkenisse, Netherlands, serving as a terminus on the Rotterdam Metro network.
  • D. Oudezijde
    Oudezijde is a historic quarter in Amsterdam’s medieval city center, known for its canals, old churches, and traditional urban fabric.
  • E. Heenweg
    Heenweg is a small village in the Dutch municipality of Westland in the province of South Holland, 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_69d886cde3d481908d4d01ba88ba7eb7 completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e3db7f6a6081909bebce3ce925e663 completed April 18, 2026, 7:29 p.m.
NED1 Entity disambiguation (via context triple) batch_6a012ed7f6fc81908d27a6581fcfa265 completed May 11, 2026, 1:20 a.m.
Created at: April 10, 2026, 5:34 a.m.