Triple
T37088115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dadra (light classical) |
E918342
|
entity |
| Predicate | allowsRagaVariation |
P193690
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Dadra (light classical), allowsRagaVariation, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowsRagaVariation Context triple: [Dadra (light classical), allowsRagaVariation, yes]
-
A.
hasRaga
Indicates that something (such as a musical piece, performance, or composition) is associated with or based on a specific raga.
-
B.
basedOnRaga
Indicates that something (such as a composition, performance, or musical element) is derived from, structured around, or primarily influenced by a particular raga.
-
C.
hasNumberOfParentRagas
Indicates the relationship specifying how many parent ragas are associated with a given raga.
-
D.
associatedWithRagaType
Indicates that something has a connection or linkage to a particular raga type.
-
E.
associatedRagaApproach
Indicates a relationship where a particular raga is linked to, or characterized by, a specific stylistic or methodological approach to performing or interpreting it.
- F. None of above. chosen
Provenance (4 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_69f76e9952b88190a6fe01ba01476520 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd4f39b5008190b83b3227ce22c509 |
completed | May 8, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69fd4df17c548190a4e2a6fea70f7e10 |
completed | May 8, 2026, 2:44 a.m. |
| PDg | Predicate description generation | batch_69fd4f38728c8190b3271abc80882cfb |
completed | May 8, 2026, 2:49 a.m. |
Created at: May 3, 2026, 4:14 p.m.