Triple
T27968280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 畲族 |
E704784
|
entity |
| Predicate | 传统音乐形式 |
P526
|
FINISHED |
| Object | 山歌 |
—
|
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: 山歌 | Statement: [畲族, 传统音乐形式, 山歌]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 传统音乐形式 Context triple: [畲族, 传统音乐形式, 山歌]
-
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.
basedInGenreTradition
Indicates that something (such as a work or practice) is grounded in, follows, or is shaped by the conventions and traditions of a particular genre.
-
C.
traditionalInstrument
Indicates that an entity is a musical instrument associated with the traditional or customary music of a particular culture, region, or community.
-
D.
inMusicCulture
Indicates that something is part of, associated with, or situated within a particular music-related cultural context or tradition.
-
E.
traditionalArtForm
Indicates that something is an established artistic practice or style that has been handed down through cultural or historical tradition.
- 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_69ef841061e48190b5570f9562f7434d |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f63b3337748190ae03ce1742a31d22 |
completed | May 2, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69f63710d17c819084cfe96e6df334fd |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 7:36 p.m.