Triple

T27697289
Position Surface form Disambiguated ID Type / Status
Subject Sundareswarar E698331 entity
Predicate templeRole P80423 FINISHED
Object co-presiding deity with Meenakshi at Meenakshi Amman Temple 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: co-presiding deity with Meenakshi at Meenakshi Amman Temple | Statement: [Sundareswarar, templeRole, co-presiding deity with Meenakshi at Meenakshi Amman Temple]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: templeRole
Context triple: [Sundareswarar, templeRole, co-presiding deity with Meenakshi at Meenakshi Amman Temple]
  • A. roleAtTemple chosen
    Indicates that an entity holds or performs a specific role, function, or position at a particular temple.
  • B. templeState
    Indicates that a temple is in a particular condition, status, or phase (such as operational, under construction, abandoned, or ceremonial).
  • C. templeType
    Indicates the specific category or classification of a temple in terms of its form, function, or religious/architectural style.
  • D. hasTempleDistrictRole
    Indicates that an entity holds a specific role or function within a temple district.
  • E. templeAccess
    Indicates that an entity has permission or the ability to enter or use a particular temple or temple-related area.
  • 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_69ef590ea74081908f0cd7500d85fa27 completed April 27, 2026, 12:39 p.m.
NER Named-entity recognition batch_69f643ed0b7481908cf25f3afec0a61d completed May 2, 2026, 6:35 p.m.
PD Predicate disambiguation batch_69f641dc8ff48190ab575d855616580c completed May 2, 2026, 6:26 p.m.
Created at: April 27, 2026, 2:55 p.m.