Triple

T9766218
Position Surface form Disambiguated ID Type / Status
Subject Bishopric of Dormagen E236996 entity
Predicate commonSpokenLanguages P42338 FINISHED
Object Middle Dutch dialects LITERAL 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: Middle Dutch dialects | Statement: [Bishopric of Dormagen, commonSpokenLanguages, Middle Dutch dialects]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: commonSpokenLanguages
Context triple: [Bishopric of Dormagen, commonSpokenLanguages, Middle Dutch dialects]
  • A. languagesSpoken
    Indicates that an entity is able to communicate using one or more specified languages.
  • B. typicalLanguages chosen
    Indicates the languages that are commonly or characteristically used, spoken, or associated with a given entity.
  • C. isWidelySpokenIn
    Indicates that a language is spoken by a large portion of the population across many regions or communities within a specified area.
  • D. includesLanguagesSpokenAlong
    Indicates that something (such as a region, route, or area) encompasses or contains the set of languages spoken along its extent or within its boundaries.
  • E. isSpokenLanguage
    Indicates that a language is used primarily for oral communication by speakers, as opposed to being only written or symbolic.
  • 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_69ca84d831b8819090322686b47887ce completed March 30, 2026, 2:12 p.m.
NER Named-entity recognition batch_69cda0a15e408190909745cb1c30937d completed April 1, 2026, 10:48 p.m.
PD Predicate disambiguation batch_69cd03d3b68c81909e570401a891b9f2 completed April 1, 2026, 11:38 a.m.
Created at: March 30, 2026, 8:25 p.m.