Triple

T4100374
Position Surface form Disambiguated ID Type / Status
Subject Sallands E87924 entity
Predicate neighboringDialect P18451 FINISHED
Object Veluws E86538 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: Veluws | Statement: [Sallands, neighboringDialect, Veluws]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Veluws
Context triple: [Sallands, neighboringDialect, Veluws]
  • A. Veluws chosen
    Veluws is a Dutch Low Saxon dialect spoken in the Veluwe region of the Netherlands, closely related to other eastern Dutch dialects such as Achterhooks.
  • B. White Park
    White Park is a public recreational park in Morgantown, West Virginia, known for its green spaces, walking trails, and community amenities.
  • C. Woensel
    Woensel is a large residential district in the northern part of the Dutch city of Eindhoven, known for its diverse population and extensive post-war housing.
  • D. Mouton
    Mouton is an academic publishing house known for its influential works in linguistics and related fields.
  • E. Rednitz
    The Rednitz is a river in Bavaria, Germany, that flows through cities such as Fürth and joins with the Pegnitz to form the Regnitz.
  • 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_69aed94564cc8190a9c1457daedb6e7f completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69aefd0d9c508190b8aedf83f3310513 completed March 9, 2026, 5:02 p.m.
NED1 Entity disambiguation (via context triple) batch_69b56b7833b081909bf5a87ee709b49f completed March 14, 2026, 2:06 p.m.
Created at: March 9, 2026, 3:40 p.m.