Triple

T1357196
Position Surface form Disambiguated ID Type / Status
Subject Songhay languages E29015 entity
Predicate hasDialectContinuum P18451 FINISHED
Object Songhay dialect continuum 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: Songhay dialect continuum | Statement: [Songhay languages, hasDialectContinuum, Songhay dialect continuum]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasDialectContinuum
Context triple: [Songhay languages, hasDialectContinuum, Songhay dialect continuum]
  • A. hasDialectContinuumWith chosen
    Indicates that two languages or dialects are part of a continuous chain of mutually intelligible varieties, without a clear boundary separating them.
  • B. hasDialects
    Indicates that an entity (typically a language) possesses one or more distinct dialectal varieties.
  • C. hasMajorDialectGroup
    Indicates that an entity (typically a language) is associated with a primary or major dialect group to which it belongs.
  • D. hasColloquialVariety
    Indicates that one linguistic form, expression, or variety is an informal, colloquial counterpart or version of another.
  • E. dominantDialect
    Indicates that one dialect is the primary or most influential form of a language within a particular context or region.
  • 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_69a498d77abc8190913bf57e5f51d2c4 completed March 1, 2026, 7:51 p.m.
NER Named-entity recognition batch_69a4c28db5048190a279ee9882caaeaf completed March 1, 2026, 10:49 p.m.
PD Predicate disambiguation batch_69a4bef7700c819099b294e8d9320e70 completed March 1, 2026, 10:34 p.m.
Created at: March 1, 2026, 7:56 p.m.