Triple
T25489429
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bhagavata Mela Natakam |
E638798
|
entity |
| Predicate | hasMusicalBasis |
P45796
|
FINISHED |
| Object | Carnatic music |
—
|
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: Carnatic music | Statement: [Bhagavata Mela Natakam, hasMusicalBasis, Carnatic music]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMusicalBasis Context triple: [Bhagavata Mela Natakam, hasMusicalBasis, Carnatic music]
-
A.
musicalBasisFor
Indicates that one musical work, idea, or element serves as the foundational source or inspiration upon which another musical work, idea, or element is built or derived.
-
B.
hasMusical
Indicates that one entity features, includes, or is associated with a musical work, performance, or musical component.
-
C.
hasMusicalForm
Indicates that one entity (typically a musical work or piece) is characterized by or structured according to a particular musical form.
-
D.
hasMusicalStyleCharacteristic
chosen
Indicates that something possesses or exhibits a particular musical style as a defining characteristic.
-
E.
hasMusicSpecialism
Indicates that an entity has a particular area of specialization or focus within the field of music.
- 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_69e75dbabeac8190bab30628f8b799d4 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f65aa07c048190a5df30d53d8f0cf5 |
completed | May 2, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f659cc571c819097e51e531961d812 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 21, 2026, 2:34 p.m.