Triple

T5790491
Position Surface form Disambiguated ID Type / Status
Subject Abzhywa dialect E128379 entity
Predicate closelyRelatedTo P37 FINISHED
Object Bzyb dialect E129310 NE 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: Bzyb dialect | Statement: [Abzhywa dialect, closelyRelatedTo, Bzyb dialect]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bzyb dialect
Context triple: [Abzhywa dialect, closelyRelatedTo, Bzyb dialect]
  • A. Bzyb dialect chosen
    The Bzyb dialect is a regional variety of the Abkhaz language traditionally spoken in the Bzyb River area of Abkhazia.
  • B. Abzhywa dialect
    The Abzhywa dialect is a major regional variety of the Abkhaz language, traditionally spoken in the Abzhywa (Abzhua) area of Abkhazia.
  • C. Babolki dialect
    The Babolki dialect is a regional variety of the Mazanderani language traditionally spoken around the city of Babol in northern Iran.
  • D. Doabi dialect
    The Doabi dialect is a regional variety of Punjabi traditionally spoken in the Doaba region of the Indian state of Punjab, between the Beas and Sutlej rivers.
  • E. Bashgal dialect
    The Bashgal dialect is a regional variety of the Kamviri language spoken by Nuristani communities in the Bashgal (Peche) Valley of eastern Afghanistan.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69c00845ca68819081a2ce3ecca577f7 completed March 22, 2026, 3:18 p.m.
NER Named-entity recognition batch_69c02a5585788190821b8da40259e0e7 completed March 22, 2026, 5:43 p.m.
NED1 Entity disambiguation (via context triple) batch_69c09820f5c08190811e848eb44ce5b9 completed March 23, 2026, 1:32 a.m.
Created at: March 22, 2026, 3:51 p.m.