Triple
T21545892
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Malwa region of Madhya Pradesh |
E531620
|
entity |
| Predicate | hasFolkMusic |
P114859
|
FINISHED |
| Object | Malwi folk songs |
—
|
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: Malwi folk songs | Statement: [Malwa region of Madhya Pradesh, hasFolkMusic, Malwi folk songs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFolkMusic Context triple: [Malwa region of Madhya Pradesh, hasFolkMusic, Malwi folk songs]
-
A.
hasFolkGenre
Indicates that something belongs to, is categorized under, or is associated with the folk music genre.
-
B.
isFolkSongFrom
Indicates that a folk song originates from or is traditionally associated with a particular place, region, or culture.
-
C.
hasMusical
Indicates that one entity features, includes, or is associated with a musical work, performance, or musical component.
-
D.
hasMusicSpecialism
Indicates that an entity has a particular area of specialization or focus within the field of music.
-
E.
hasMusicCategory
chosen
Indicates that something is associated with, classified under, or belongs to a particular category or type 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_69e0c45f17148190949c330ab9c27706 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eeb58ef2548190a81ff51baba76e48 |
completed | April 27, 2026, 1:02 a.m. |
| PD | Predicate disambiguation | batch_69e6320766308190ba5dca2f7c826aa4 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:28 p.m.