Triple

T35764945
Position Surface form Disambiguated ID Type / Status
Subject Western South Slavic languages E1033988 entity
Predicate shareIsoglossesWith P10344 FINISHED
Object Central South Slavic dialects 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: Central South Slavic dialects | Statement: [Western South Slavic languages, shareIsoglossesWith, Central South Slavic dialects]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: shareIsoglossesWith
Context triple: [Western South Slavic languages, shareIsoglossesWith, Central South Slavic dialects]
  • A. sharesIsoglossWith chosen
    Indicates that two linguistic varieties share a common isogloss, i.e., they exhibit the same geographically bounded linguistic feature or boundary.
  • B. sharesLanguageWith
    Indicates that two entities use at least one common language for communication.
  • C. shareLanguageInfluence
    Indicates that two entities affect or shape each other’s language use, development, or characteristics through mutual or shared influence.
  • D. hasDialectalFeaturesSharedWith
    Indicates that two language varieties share specific dialectal features or characteristics in common.
  • E. hasDialectContinuumWith
    Indicates that two languages or dialects are part of a continuous chain of mutually intelligible varieties, without a clear boundary separating them.
  • 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_69f76e13edd081909101629aa829c4ad completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_6a00708ab11081909641d245c4282aa0 completed May 10, 2026, 11:48 a.m.
PD Predicate disambiguation batch_6a00703daa0081908903ce3a28084d35 completed May 10, 2026, 11:47 a.m.
Created at: May 3, 2026, 4:06 p.m.