Triple

T27496855
Position Surface form Disambiguated ID Type / Status
Subject Goddess Meenakshi E694039 entity
Predicate primaryScriptureContext P6572 FINISHED
Object Tamil Shaiva literature NE NERFINISHED

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: Tamil Shaiva literature | Statement: [Goddess Meenakshi, primaryScriptureContext, Tamil Shaiva literature]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: primaryScriptureContext
Context triple: [Goddess Meenakshi, primaryScriptureContext, Tamil Shaiva literature]
  • A. scriptureContext chosen
    Indicates that one entity provides the textual, historical, or thematic scriptural background or setting necessary to interpret or understand another entity.
  • B. scripturalSetting
    Indicates the contextual or narrative situation in which a scriptural passage or event takes place.
  • C. scripturalLanguageContext
    Indicates the linguistic or textual context in which a scriptural passage, term, or reference is expressed or interpreted.
  • D. regionInScripturalContext
    Indicates that a geographic region is referenced or holds significance within a particular scriptural or religious text context.
  • E. positionInScripture
    Indicates the specific location or ordering of a passage, verse, or element within a scriptural text.
  • 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_69ef538370888190b1ddf53bb4831188 completed April 27, 2026, 12:16 p.m.
NER Named-entity recognition batch_69ff519b65f081909902ba83b775ef85 completed May 9, 2026, 3:24 p.m.
PD Predicate disambiguation batch_69ff506fccdc8190bd93269589040aed completed May 9, 2026, 3:19 p.m.
Created at: April 27, 2026, 1:09 p.m.