Triple

T26125139
Position Surface form Disambiguated ID Type / Status
Subject Brahma Sampradaya E659079 entity
Predicate regardsMadhvacharyaAs P159976 FINISHED
Object acharya 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: acharya | Statement: [Brahma Sampradaya, regardsMadhvacharyaAs, acharya]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: regardsMadhvacharyaAs
Context triple: [Brahma Sampradaya, regardsMadhvacharyaAs, acharya]
  • A. regards
    Indicates that one entity considers, views, or treats another entity in a particular way or with a certain attitude.
  • B. honorsNimbarkaAs
    Indicates that someone regards Nimbarka with a particular status, role, or title, such as a teacher, authority, or incarnation.
  • C. regardsPrayerAs
    Indicates that one entity holds a particular attitude, evaluation, or characterization toward prayer as a practice or concept.
  • D. associatedWithAcharya
    Indicates a relationship in which an entity is connected, linked, or related in some relevant way to an acharya (a spiritual or scholarly teacher).
  • E. associatedWithMahavakya
    Indicates a relationship in which something is connected or related to a Mahavakya (a great Vedic or Upanishadic saying), typically by expressing, embodying, or being derived from it.
  • 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_69ee5bc2b2948190b458ad3f580af779 completed April 26, 2026, 6:38 p.m.
NER Named-entity recognition batch_69f60ad0714c8190b22f7a912cad364e completed May 2, 2026, 2:31 p.m.
PD Predicate disambiguation batch_69f5b0021da88190bdd4cf2698c23edf completed May 2, 2026, 8:04 a.m.
PDg Predicate description generation batch_69f5f6b32a8881909baa0db57b80d56a completed May 2, 2026, 1:05 p.m.
Created at: April 26, 2026, 8:11 p.m.