Triple

T25683961
Position Surface form Disambiguated ID Type / Status
Subject Goddess Kamakhya E644016 entity
Predicate mainSanctumSymbol P5607 FINISHED
Object natural rock cleft representing yoni 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: natural rock cleft representing yoni | Statement: [Goddess Kamakhya, mainSanctumSymbol, natural rock cleft representing yoni]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: mainSanctumSymbol
Context triple: [Goddess Kamakhya, mainSanctumSymbol, natural rock cleft representing yoni]
  • A. hasMainSanctum
    Indicates that an entity possesses a primary or central sacred space used for core religious or spiritual activities.
  • B. centralDeitySymbol
    Indicates that one entity serves as the primary or central symbolic representation of a deity for another entity.
  • C. sanctumContains
    Indicates that one sanctum or sacred space physically or conceptually includes or holds another entity within its bounds.
  • D. mainSaint
    Indicates that one entity is recognized as the principal or patron saint associated with another entity (such as a place, institution, or group).
  • E. hasSacredSymbol chosen
    Indicates that one entity serves as a sacred or religiously significant symbol associated with another entity.
  • 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_69e77e8046888190b07ffa58c7e2c37a completed April 21, 2026, 1:41 p.m.
NER Named-entity recognition batch_69f600c18a14819081b5914dd3b0f9cf completed May 2, 2026, 1:48 p.m.
PD Predicate disambiguation batch_69f5f7fba5248190945acf1561280799 completed May 2, 2026, 1:11 p.m.
Created at: April 21, 2026, 8:05 p.m.