Triple

T6046357
Position Surface form Disambiguated ID Type / Status
Subject Ekadanta E134674 entity
Predicate hasDevotees P21326 FINISHED
Object Hindus across various sects 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: Hindus across various sects | Statement: [Ekadanta, hasDevotees, Hindus across various sects]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasDevotees
Context triple: [Ekadanta, hasDevotees, Hindus across various sects]
  • A. devoteesSeek
    Indicates that devoted followers actively seek out, pursue, or strive to approach the object of their devotion.
  • B. associatedDevotion chosen
    Indicates a relationship where one entity is linked to or characterized by a particular devotion, dedication, or religious/spiritual practice connected to another entity.
  • C. veneratedBy
    Indicates that one entity is regarded with deep respect, reverence, or worship by another entity.
  • D. isConsideredByAdherents
    Indicates that something (such as a belief, practice, object, or figure) is regarded or held in a particular way by the people who adhere to a specific faith, ideology, or group.
  • E. hasDeity
    Indicates that one entity recognizes, worships, or is associated with another entity as its deity or divine figure.
  • 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_69c00876a69881908088a2626d3b2666 completed March 22, 2026, 3:19 p.m.
NER Named-entity recognition batch_69c056e53f508190864be04bc016c525 completed March 22, 2026, 8:53 p.m.
PD Predicate disambiguation batch_69c049eb52a08190ac10fd703735f5aa completed March 22, 2026, 7:58 p.m.
Created at: March 22, 2026, 4:09 p.m.