Triple
T31924144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nottuswaras |
E815054
|
entity |
| Predicate | commonTala |
P89832
|
FINISHED |
| Object | Adi tala |
—
|
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: Adi tala | Statement: [Nottuswaras, commonTala, Adi tala]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonTala Context triple: [Nottuswaras, commonTala, Adi tala]
-
A.
isMostCommonTala
Indicates that a given tāla (rhythmic cycle) is the most frequently used or prevalent among a set of tālas.
-
B.
associatedTala
chosen
Indicates a relationship where something (such as a musical piece, performance, or pattern) is linked to or governed by a specific tala (rhythmic cycle).
-
C.
commonIn
Indicates that something frequently occurs, appears, or is found within a specified context, group, or environment.
-
D.
talaBeats
Indicates a rhythmic relationship where one entity provides or marks the beats or rhythmic cycle (tala) that structure another entity’s timing or performance.
-
E.
isReferenceTala
Indicates that one entity serves as a reference or canonical example for the tala (rhythmic cycle) associated with another entity.
- 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_69f348f1df848190851bbfb988da3414 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe066d62b48190867df334039be786 |
completed | May 8, 2026, 3:51 p.m. |
| PD | Predicate disambiguation | batch_69fe03afde3c8190a5b9b0778d19eb1a |
completed | May 8, 2026, 3:39 p.m. |
Created at: May 1, 2026, 12:03 a.m.