Triple

T1529303
Position Surface form Disambiguated ID Type / Status
Subject Rayalaseema Telugu E32403 entity
Predicate hasVariationWithin P455 FINISHED
Object district-level subdialects in Rayalaseema 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: district-level subdialects in Rayalaseema | Statement: [Rayalaseema Telugu, hasVariationWithin, district-level subdialects in Rayalaseema]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasVariationWithin
Context triple: [Rayalaseema Telugu, hasVariationWithin, district-level subdialects in Rayalaseema]
  • A. hasVariability
    Indicates that an entity exhibits variation or fluctuation in its state, value, or characteristics over time or across instances.
  • B. hasVariance
    Indicates that there is a measurable degree of variability or dispersion in the values or outcomes associated with the related entities.
  • C. hasVariant chosen
    Indicates that one entity exists as an alternative form, version, or variation of another entity.
  • D. hasVariantSeries
    Indicates a relationship where one entity is a variant or alternative series derived from or associated with another series.
  • E. viewVariesAmong
    Indicates that the way something is viewed, perceived, or interpreted differs across multiple entities or contexts.
  • 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_69a885ea86308190998f6bc14bb91f8e completed March 4, 2026, 7:20 p.m.
NER Named-entity recognition batch_69a933ddc5a881909cdf503f2bc29bd4 completed March 5, 2026, 7:42 a.m.
PD Predicate disambiguation batch_69a907ae8f688190ad9000ea1e018585 completed March 5, 2026, 4:33 a.m.
Created at: March 4, 2026, 7:26 p.m.