Triple

T27634994
Position Surface form Disambiguated ID Type / Status
Subject Flemish dialect continuum E696444 entity
Predicate standardizationBasedOn P1371 FINISHED
Object Standard Dutch NE NERFINISHED

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: Standard Dutch | Statement: [Flemish dialect continuum, standardizationBasedOn, Standard Dutch]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: standardizationBasedOn
Context triple: [Flemish dialect continuum, standardizationBasedOn, Standard Dutch]
  • A. standardizedBy chosen
    Indicates that one entity defines, regulates, or formalizes the standards or specifications by which another entity is created, measured, or operated.
  • B. standardizationApproach
    Indicates the method or strategy used to establish, implement, or align with a common standard across entities or processes.
  • C. standardizedIn
    Indicates that something has been formally defined, regulated, or made uniform within a particular standard, framework, or jurisdiction.
  • D. standardizationAspect
    Indicates the specific dimension or feature of something that is being standardized or brought into conformity with a standard.
  • E. standardizedFor
    Indicates that something has been adjusted or converted to conform to a common standard, format, or reference so it can be consistently compared or used.
  • F. None of above.

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_69ef5909f3848190805f35b76833e722 completed April 27, 2026, 12:39 p.m.
NER Named-entity recognition batch_69f66c5c13808190887180099745673b completed May 2, 2026, 9:27 p.m.
PD Predicate disambiguation batch_69f66abddc448190a488852f8abdeb2c completed May 2, 2026, 9:21 p.m.
Created at: April 27, 2026, 2:23 p.m.