Triple

T5704653
Position Surface form Disambiguated ID Type / Status
Subject Languages of India E125754 entity
Predicate hasClassicalLanguage P65683 FINISHED
Object Sanskrit 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: Sanskrit | Statement: [Languages of India, hasClassicalLanguage, Sanskrit]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasClassicalLanguage
Context triple: [Languages of India, hasClassicalLanguage, Sanskrit]
  • A. mainClassicalLanguage
    Indicates the primary classical (historically foundational) language associated with an entity, such as a text, culture, or scholarly tradition.
  • B. recognizedAsClassicalLanguageBy
    Indicates that an entity is acknowledged or designated by a specified authority or source as a classical language.
  • C. includesMajorLanguageFamily
    Indicates that one entity encompasses, contains, or is associated with a major language family as part of its scope or classification.
  • D. linguisticClassification
    Indicates the relationship by which an entity is categorized according to its language or linguistic type.
  • E. isInLanguageFamily
    Indicates that a language belongs to, or is classified within, a particular language family based on shared linguistic ancestry or characteristics.
  • F. None of above. chosen

Provenance (4 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_69c0082c96988190b3a6a201edce472a completed March 22, 2026, 3:18 p.m.
NER Named-entity recognition batch_69c024585d14819098ec34fd5a858836 completed March 22, 2026, 5:18 p.m.
PD Predicate disambiguation batch_69c021c2d8bc8190b947c7d1f423d2f3 completed March 22, 2026, 5:07 p.m.
PDg Predicate description generation batch_69c023dfec6881909ee6189b874b4348 completed March 22, 2026, 5:16 p.m.
Created at: March 22, 2026, 3:45 p.m.