Triple

T21479168
Position Surface form Disambiguated ID Type / Status
Subject Ambaji E529940 entity
Predicate isKuldeviFor P144511 FINISHED
Object many Gujarati communities 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: many Gujarati communities | Statement: [Ambaji, isKuldeviFor, many Gujarati communities]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isKuldeviFor
Context triple: [Ambaji, isKuldeviFor, many Gujarati communities]
  • A. isDivyaDesam
    Indicates that a location is one of the 108 sacred Vishnu temples (Divya Desams) revered in the Tamil Vaishnavite tradition.
  • B. isPancharangaKshetram
    Indicates that a temple or sacred site is recognized as one of the Pancharanga Kshetrams, the five traditional holy shrines dedicated to Lord Ranganatha (Vishnu) along the Kaveri river.
  • C. hasNumberOfDivyaDesams
    Indicates the specific count of Divya Desams associated with a given entity.
  • D. devotionPracticedBy
    Indicates that a particular form of devotion, worship, or religious practice is performed or carried out by a specified agent or practitioner.
  • E. isDevotedTo
    Indicates a strong, enduring commitment or dedication that one entity directs toward another.
  • 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_69e0c45acc3881908e38d3f28964152b completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69e9ea1a37a88190845810cbcacbad65 completed April 23, 2026, 9:44 a.m.
PD Predicate disambiguation batch_69e631ec1d048190b6da97da8222e413 completed April 20, 2026, 2:02 p.m.
PDg Predicate description generation batch_69e6386c5a4481909c37f7de7e9fc025 completed April 20, 2026, 2:30 p.m.
Created at: April 16, 2026, 6:20 p.m.