Triple

T19593853
Position Surface form Disambiguated ID Type / Status
Subject Madhyandina Upaniṣad tradition E470301 entity
Predicate usesScripturalCategory P80557 FINISHED
Object Śruti 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: Śruti | Statement: [Madhyandina Upaniṣad tradition, usesScripturalCategory, Śruti]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usesScripturalCategory
Context triple: [Madhyandina Upaniṣad tradition, usesScripturalCategory, Śruti]
  • A. scripturalUse
    Indicates that one entity is used as a scriptural reference, source, or basis within the context or content of another entity.
  • B. usesScriptureType chosen
    Indicates that one entity employs or is based on a particular type or classification of scripture.
  • C. scripturalExpertise
    Indicates a relationship where one entity possesses specialized knowledge or authoritative understanding of religious scriptures in relation to another entity or context.
  • D. hasScripture
    Indicates that one entity possesses, is associated with, or is defined by a particular scripture or set of scriptural texts.
  • E. scripturalStatus
    Indicates the relationship between a text and its recognition or classification as scriptural, canonical, or authoritative within a religious or doctrinal tradition.
  • 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_69d8e510024481908415c0d616fa6186 completed April 10, 2026, 11:54 a.m.
NER Named-entity recognition batch_69e640782e2c8190b5baef07a2bdd015 completed April 20, 2026, 3:04 p.m.
PD Predicate disambiguation batch_69e514dbdb988190b55931a8138c73e7 completed April 19, 2026, 5:46 p.m.
Created at: April 10, 2026, 1:43 p.m.