Triple

T34076078
Position Surface form Disambiguated ID Type / Status
Subject Shabad E873910 entity
Predicate musicallyRenderedWith P194715 FINISHED
Object Kirtan instruments 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: Kirtan instruments | Statement: [Shabad, musicallyRenderedWith, Kirtan instruments]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: musicallyRenderedWith
Context triple: [Shabad, musicallyRenderedWith, Kirtan instruments]
  • A. musicallyRenderedIn chosen
    Indicates that something (such as a work, scene, or content) is presented or expressed through a musical performance or composition in a particular context.
  • B. musicalDepictionOf
    Indicates that one entity is a musical work that artistically represents, portrays, or is inspired by another entity.
  • C. hasMusical
    Indicates that one entity features, includes, or is associated with a musical work, performance, or musical component.
  • D. governedByInstrument
    Indicates that an action, process, or state is carried out, regulated, or controlled through the use of a specific instrument or tool.
  • E. musicDriven
    Indicates that one entity’s behavior, structure, or progression is guided, influenced, or determined primarily by music or musical elements.
  • 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_69f349a566808190a1c63b898f33cddf completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69fd864235b481908738dbb69556bc62 completed May 8, 2026, 6:44 a.m.
PD Predicate disambiguation batch_69fd8373b6bc819091c554f29ee17fec completed May 8, 2026, 6:32 a.m.
Created at: May 1, 2026, 1:52 a.m.