Triple

T3737385
Position Surface form Disambiguated ID Type / Status
Subject Balkan Latin E79617 entity
Predicate instanceOf P0 FINISHED
Object hypothesized regional variety of Vulgar Latin C4907 CONCEPT FINISHED

How this triple was built (1 step)

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.

CD Concept disambiguation gpt-5-mini-2025-08-07
Target class: hypothesized regional variety of Vulgar Latin
Context triple: [Balkan Latin, instanceOf, hypothesized regional variety of Vulgar Latin]
  • A. Romance language variety
    A Romance language variety is a specific form or dialect of a Romance language, distinguished by its unique phonological, grammatical, and lexical features within the broader Romance language family.
  • B. Gallo-Italic language
    A Gallo-Italic language is a member of a group of Romance languages spoken primarily in northern Italy and parts of Switzerland, characterized by features intermediate between Gallo-Romance (like French) and Italo-Romance (like standard Italian).
  • C. classical language variety
    A classical language variety is a historically prestigious, standardized form of a language, typically preserved in literature and formal contexts, that differs from its modern spoken descendants.
  • D. Eastern Romance language chosen
    An Eastern Romance language is a member of the Romance branch of the Indo-European language family that evolved from Eastern varieties of Vulgar Latin, primarily spoken in the Balkans and surrounding regions.
  • E. medieval North Germanic language variety
    A medieval North Germanic language variety is a historical form of a Scandinavian language spoken in Northern Europe during the Middle Ages, characterized by its distinct phonology, morphology, and vocabulary relative to both earlier Norse and later modern Scandinavian languages.
  • F. None of above.

Provenance (1 batch)

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_69ad8b115610819095b02007da5ca3cb completed March 8, 2026, 2:43 p.m.
Created at: March 8, 2026, 3:34 p.m.