Triple
T37088080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dadra (light classical) |
E918342
|
entity |
| Predicate | talaBeats |
P187125
|
FINISHED |
| Object | 6 |
—
|
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: 6 | Statement: [Dadra (light classical), talaBeats, 6]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: talaBeats Context triple: [Dadra (light classical), talaBeats, 6]
-
A.
usesBeatFrom
Indicates that one entity employs or incorporates the rhythmic pattern, instrumental backing, or beat originally created for or associated with another entity.
-
B.
beatboxer
Indicates that an entity performs vocal percussion or imitates drum sounds using their mouth, lips, tongue, and voice.
-
C.
notableTune
Indicates that a tune is especially significant, well-known, or characteristic in relation to a particular entity.
-
D.
musicHub
Indicates a relationship where one entity serves as a central source, platform, or focal point for music-related content, activities, or connections for another entity.
-
E.
isMostCommonTala
Indicates that a given tāla (rhythmic cycle) is the most frequently used or prevalent among a set of tālas.
- 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_69fb344c60f8819090f2e21e1e61d621 |
completed | May 6, 2026, 12:30 p.m. |
| PD | Predicate disambiguation | batch_69fb2f642db08190b562725502c74ea6 |
completed | May 6, 2026, 12:09 p.m. |
| PDg | Predicate description generation | batch_69fb344ba5408190a6fe8face293d88b |
completed | May 6, 2026, 12:30 p.m. |
Created at: May 3, 2026, 4:14 p.m.