Triple

T6510022
Position Surface form Disambiguated ID Type / Status
Subject Konjo language E150102 entity
Predicate dialectalDivision P1762 FINISHED
Object coastal vs. highland varieties 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: coastal vs. highland varieties | Statement: [Konjo language, dialectalDivision, coastal vs. highland varieties]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: dialectalDivision
Context triple: [Konjo language, dialectalDivision, coastal vs. highland varieties]
  • A. hasDialectContinuumWith
    Indicates that two languages or dialects are part of a continuous chain of mutually intelligible varieties, without a clear boundary separating them.
  • B. regionalDialect chosen
    Indicates that one entity uses or is associated with a dialect specific to a particular geographic region in relation to another entity.
  • C. majorDialectOf
    Indicates that one dialect is the primary or most prominent dialect associated with a particular language or region.
  • D. notableDialect
    Indicates that an entity is recognized for having a distinct or noteworthy dialect associated with it.
  • 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_69c687ef291081909d437f035eef1cda completed March 27, 2026, 1:36 p.m.
NER Named-entity recognition batch_69c69f398f10819096342f3646cefcc2 completed March 27, 2026, 3:16 p.m.
PD Predicate disambiguation batch_69c68ab98c78819081743e614df04e1d completed March 27, 2026, 1:48 p.m.
Created at: March 27, 2026, 1:43 p.m.