Triple
T31645233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arabhi |
E807567
|
entity |
| Predicate | usesChatusrutiDhaivata |
P155983
|
FINISHED |
| Object | D2 |
—
|
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: D2 | Statement: [Arabhi, usesChatusrutiDhaivata, D2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesChatusrutiDhaivata Context triple: [Arabhi, usesChatusrutiDhaivata, D2]
-
A.
usesChatusrutiRishabha
Indicates that one entity employs or incorporates the Chatusruti Rishabha (a specific swara/scale degree) in relation to another entity, such as in a musical composition, scale, or performance.
-
B.
hasDrutamAksharas
Indicates that something possesses or is associated with a specific number of drutam rhythmic units (aksharas) in a metrical or musical context.
-
C.
usesSwaras
chosen
Indicates that one entity employs or incorporates specific musical notes (swaras) in relation to another entity or context.
-
D.
hasDhaivatam
Indicates that one musical entity possesses or includes the note "Dhaivatam" within its structure or scale.
-
E.
usesShuddhaSwaras
Indicates that an entity employs only the pure (shuddha) notes of the scale, without incorporating altered or variant swaras.
- 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_69f348d9ce58819093ea2da83cbeeec1 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fd09840ea88190a2e6d7e577ade717 |
completed | May 7, 2026, 9:52 p.m. |
| PD | Predicate disambiguation | batch_69fd064c49988190afadddbd04d7cb94 |
completed | May 7, 2026, 9:38 p.m. |
Created at: April 30, 2026, 10:50 p.m.