Triple

T25282497
Position Surface form Disambiguated ID Type / Status
Subject Mridangam E633856 entity
Predicate hasTuningProperty P135075 FINISHED
Object tuned to tonic of main performer 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: tuned to tonic of main performer | Statement: [Mridangam, hasTuningProperty, tuned to tonic of main performer]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasTuningProperty
Context triple: [Mridangam, hasTuningProperty, tuned to tonic of main performer]
  • A. tuningType
    Indicates the specific method or configuration by which something is adjusted or calibrated to achieve a desired performance or behavior.
  • B. usesTuningReference chosen
    Indicates that one entity adopts another entity as the pitch or frequency standard for tuning.
  • C. isTunedTo
    Indicates that one entity has been adjusted or configured to operate at, receive, or correspond to the frequency, channel, or setting of another entity.
  • D. hasTuningDivision
    Indicates that one entity specifies or uses a particular system or scheme for dividing a range (such as a musical interval or scale) into tuning units.
  • E. haveProperty
    Indicates that an entity possesses, exhibits, or is characterized by a particular property or attribute.
  • 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_69e75a9402fc81909362ca85277c06d9 completed April 21, 2026, 11:08 a.m.
NER Named-entity recognition batch_69f48e0560648190bb88db7255867d7f completed May 1, 2026, 11:27 a.m.
PD Predicate disambiguation batch_69f45d06d0388190b36ecde92013624a completed May 1, 2026, 7:57 a.m.
Created at: April 21, 2026, 1:19 p.m.