Triple

T27909160
Position Surface form Disambiguated ID Type / Status
Subject Basavakalyan Fort E705873 entity
Predicate associatedWithReligionOrMovement P17590 FINISHED
Object Lingayat movement 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: Lingayat movement | Statement: [Basavakalyan Fort, associatedWithReligionOrMovement, Lingayat movement]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: associatedWithReligionOrMovement
Context triple: [Basavakalyan Fort, associatedWithReligionOrMovement, Lingayat movement]
  • A. associatedReligionOrBelief
    Indicates that an entity is connected to, identified with, or characterized by a particular religion or belief system.
  • B. associatedReligionText
    Indicates that there is a textual work (such as a scripture or religious document) that is specifically associated with, or pertains to, a given religion.
  • C. hasReligiousMovement chosen
    Indicates that an entity is associated with, follows, or is characterized by a particular religious movement.
  • D. hasAssociatedReligion
    Indicates that an entity is connected with or linked to a particular religion.
  • E. associatedWithReligiousEvent
    Indicates a relationship where something is connected or related to a specific religious event or ceremony.
  • 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_69ef96b5aad08190be36a277c31e7004 completed April 27, 2026, 5:02 p.m.
NER Named-entity recognition batch_6a008b8938608190adaccbd720111a18 completed May 10, 2026, 1:43 p.m.
PD Predicate disambiguation batch_6a008b24baac8190baaaf50c2e9cc6bd completed May 10, 2026, 1:41 p.m.
Created at: April 27, 2026, 6:48 p.m.