Triple

T14401737
Position Surface form Disambiguated ID Type / Status
Subject Vogul language E357087 entity
Predicate hasStandardVarietyBasedOn P95273 FINISHED
Object Northern Mansi dialect 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: Northern Mansi dialect | Statement: [Vogul language, hasStandardVarietyBasedOn, Northern Mansi dialect]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasStandardVarietyBasedOn
Context triple: [Vogul language, hasStandardVarietyBasedOn, Northern Mansi dialect]
  • A. standardVarietyBasedIn
    Indicates that a standard or reference variety (such as a language or dialect) is primarily established, recognized, or centered in a particular location or region.
  • B. hasVarietyOf
    Indicates that an entity possesses or offers multiple different types, forms, or versions of something.
  • C. isRecognizedAsVarietyOf chosen
    Indicates that one entity is acknowledged or classified as a specific variety or subtype of another entity.
  • D. hasStandardSeries
    Indicates that an entity is associated with, or belongs to, a designated standard series or standardized sequence.
  • E. hasApproximateNumberOfVarieties
    Indicates that an entity is associated with an estimated or non-exact count of different varieties or types.
  • 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_69d827927c988190ad98bb0360981783 completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de908500048190bb6a20fe318d5c62 completed April 14, 2026, 7:07 p.m.
PD Predicate disambiguation batch_69de2aa024c48190805df6a9d63deb10 completed April 14, 2026, 11:53 a.m.
Created at: April 10, 2026, 1:17 a.m.