Triple
T27524612
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | sheng |
E694799
|
entity |
| Predicate | inMusicTradition |
P526
|
FINISHED |
| Object | Chinese folk music |
—
|
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: Chinese folk music | Statement: [sheng, inMusicTradition, Chinese folk music]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inMusicTradition Context triple: [sheng, inMusicTradition, Chinese folk music]
-
A.
musicTradition
chosen
Indicates a relationship where one entity follows, embodies, or belongs to a particular musical tradition or style associated with another entity.
-
B.
inMusicCulture
Indicates that something is part of, associated with, or situated within a particular music-related cultural context or tradition.
-
C.
inMusicology
Indicates that something is studied, analyzed, or treated within the academic field or disciplinary context of musicology.
-
D.
notableRecordingTradition
Indicates that there exists a significant or historically important tradition of recording or documenting something associated with the subject.
-
E.
isFolkSongFrom
Indicates that a folk song originates from or is traditionally associated with a particular place, region, or culture.
- 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_69ef538550208190aa9de8e2cb260d93 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f62f2e2df88190948551f6fd67a65a |
completed | May 2, 2026, 5:06 p.m. |
| PD | Predicate disambiguation | batch_69f62c1762f881908c25e8f70ecd5041 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 1:23 p.m.