Triple

T30682595
Position Surface form Disambiguated ID Type / Status
Subject Vienna Literary Agreement E781093 entity
Predicate dialectalBasis P114079 FINISHED
Object Neo-Shtokavian 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: Neo-Shtokavian dialect | Statement: [Vienna Literary Agreement, dialectalBasis, Neo-Shtokavian dialect]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: dialectalBasis
Context triple: [Vienna Literary Agreement, dialectalBasis, Neo-Shtokavian dialect]
  • A. dialectDocumentation
    Indicates that there exists documentation or descriptive information specifically about a particular dialect or dialectal variety.
  • B. isDialectalBaseOf chosen
    Indicates that one language variety serves as the primary dialectal source or foundation from which another dialect develops or is derived.
  • C. hasDialectContinuumWith
    Indicates that two languages or dialects are part of a continuous chain of mutually intelligible varieties, without a clear boundary separating them.
  • D. dialectFamily
    Indicates that one dialect belongs to, or is classified under, a particular dialect family.
  • E. regionalDialect
    Indicates that one entity uses or is associated with a dialect specific to a particular geographic region in relation to another entity.
  • 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_69f224a92f54819095499b4d32bd5134 completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69f68b81f12c8190a0aaacc0a54f9db5 completed May 2, 2026, 11:40 p.m.
PD Predicate disambiguation batch_69f6861170d08190bb98be609d436f84 completed May 2, 2026, 11:17 p.m.
Created at: April 29, 2026, 8:33 p.m.