Triple

T12295718
Position Surface form Disambiguated ID Type / Status
Subject Oldehove E293080 entity
Predicate hasMinorityLanguage P2267 FINISHED
Object Gronings E411393 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: Gronings | Statement: [Oldehove, hasMinorityLanguage, Gronings]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Gronings
Context triple: [Oldehove, hasMinorityLanguage, Gronings]
  • A. Gronings chosen
    Gronings is a Low Saxon dialect spoken in the province of Groningen in the Netherlands, known for its distinct phonology and vocabulary within the Dutch Low Saxon language group.
  • B. Greven
    Greven is a town in the Münsterland region of North Rhine-Westphalia in western Germany, known for its proximity to Münster and its role as a local economic and transport hub.
  • C. Gelderlander
    Gelderlander is a regional Dutch newspaper based in the province of Gelderland.
  • D. Gronau
    Gronau is a town in Germany historically noted as the site of a battle during the Seven Years' War.
  • E. Niederlauer
    Niederlauer is a small municipality in northern Bavaria, Germany, situated in the Franconian Saale valley and known for its rural character within the Rhön region.
  • 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_69d6ab690ad081908c0ed3870ec82d53 completed April 8, 2026, 7:24 p.m.
NER Named-entity recognition batch_69d93ed903808190b7ed90e0db3d7586 completed April 10, 2026, 6:18 p.m.
NED1 Entity disambiguation (via context triple) batch_69f61e79bf548190bf7f314222ed1ed1 completed May 2, 2026, 3:55 p.m.
Created at: April 8, 2026, 9:52 p.m.