Triple

T31692784
Position Surface form Disambiguated ID Type / Status
Subject Goula E808836 entity
Predicate thaatEquivalent P172050 FINISHED
Object Bhairav (approximate, Hindustani) 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: Bhairav (approximate, Hindustani) | Statement: [Goula, thaatEquivalent, Bhairav (approximate, Hindustani)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: thaatEquivalent
Context triple: [Goula, thaatEquivalent, Bhairav (approximate, Hindustani)]
  • A. thaatEquivalentInHindustani chosen
    Indicates that two musical elements are equivalent or correspond to the same thaat (parent scale) within the Hindustani music system.
  • B. equivalentIn
    Indicates that two entities are considered logically or functionally the same in meaning, status, or effect within a given context.
  • C. equivalentInTibet
    Indicates that two entities are considered equivalent or correspond to each other within the context of Tibet.
  • D. hasExactImperialEquivalent
    Indicates that one measurement or quantity has a directly corresponding and precisely equal value in the imperial system.
  • E. languageEquivalent
    Indicates that two linguistic expressions convey the same meaning or function across different languages or language varieties.
  • 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_69f348ddcbc48190950cabcc25ff29b3 completed April 30, 2026, 12:19 p.m.
NER Named-entity recognition batch_69f6aaf50be08190a2b62a6d881f8aee completed May 3, 2026, 1:55 a.m.
PD Predicate disambiguation batch_69f6aa20a1588190a53533fc9764efb2 completed May 3, 2026, 1:51 a.m.
Created at: April 30, 2026, 11:09 p.m.