Triple

T25230535
Position Surface form Disambiguated ID Type / Status
Subject Virupaksha Temple, Hampi E632207 entity
Predicate earlierSanctity P146079 FINISHED
Object associated with Pampa Tirtha 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: associated with Pampa Tirtha | Statement: [Virupaksha Temple, Hampi, earlierSanctity, associated with Pampa Tirtha]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: earlierSanctity
Context triple: [Virupaksha Temple, Hampi, earlierSanctity, associated with Pampa Tirtha]
  • A. earlierPhaseReligion
    Indicates that one religious phase, tradition, or development chronologically precedes another in a given historical or doctrinal sequence.
  • B. veneratedBefore chosen
    Indicates that one entity was honored or revered at an earlier time or prior to another entity.
  • C. hasSanctityComparableTo
    Indicates that one entity possesses a level or quality of sanctity that is comparable to that of another entity.
  • D. sacredTo
    Indicates that one entity is regarded as holy, revered, or dedicated in honor of another entity, such as a deity, person, or concept.
  • E. sacredStatus
    Indicates that something holds a revered, holy, or religiously significant status within a particular belief system or 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_69e75a8e0f688190a7aebe9a4815e25b completed April 21, 2026, 11:07 a.m.
NER Named-entity recognition batch_69f47cc7199c8190bf32bd5aa0090e07 completed May 1, 2026, 10:13 a.m.
PD Predicate disambiguation batch_69f4683472ec8190a483b3b8afe71720 completed May 1, 2026, 8:45 a.m.
Created at: April 21, 2026, 1:04 p.m.