Triple

T8710119
Position Surface form Disambiguated ID Type / Status
Subject Digil E206752 entity
Predicate hasDialectClusterStatus P24201 FINISHED
Object major dialect cluster of Somali 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: major dialect cluster of Somali | Statement: [Digil, hasDialectClusterStatus, major dialect cluster of Somali]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasDialectClusterStatus
Context triple: [Digil, hasDialectClusterStatus, major dialect cluster of Somali]
  • A. hasDialectStatus chosen
    Indicates that one language variety holds a particular dialect-related status or classification in relation to another language or linguistic standard.
  • B. hasDialectsIn
    Indicates that a language or linguistic variety possesses distinct dialects that are used or found within a specified region or context.
  • C. hasDialects
    Indicates that an entity (typically a language) possesses one or more distinct dialectal varieties.
  • D. hasPrimaryClusterIn
    Indicates that an entity’s main or most significant cluster is located within or associated with a specified cluster or grouping.
  • E. hasDialectCounterpart
    Indicates that one linguistic form or expression has a corresponding equivalent in another dialect.
  • 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_69ca835645e881908f00e3c8b51da81d completed March 30, 2026, 2:06 p.m.
NER Named-entity recognition batch_69cc5c3034708190b895eaf890d62198 completed March 31, 2026, 11:43 p.m.
PD Predicate disambiguation batch_69cc456bda508190a9aa0fb92760739e completed March 31, 2026, 10:06 p.m.
Created at: March 30, 2026, 6:35 p.m.