Triple
T27270703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qinqiang |
E688043
|
entity |
| Predicate | hasBoldSingingStyle |
P175975
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Qinqiang, hasBoldSingingStyle, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBoldSingingStyle Context triple: [Qinqiang, hasBoldSingingStyle, true]
-
A.
hasSecondaryVocalStyle
Indicates that an entity (typically a performer or recording) employs an additional, non-primary vocal style alongside its main vocal style.
-
B.
hasHookVocalStyle
Indicates that an entity (typically a musical work or performance) features a distinctive, catchy vocal delivery or refrain intended to serve as a memorable hook.
-
C.
introducedVocalStyleOf
Indicates that one entity initiated or brought into use the vocal style characteristic of another entity.
-
D.
hasVocalStyleComparedTo
Indicates a comparison between entities based on the similarity or resemblance of their vocal style.
-
E.
hasMusicalVocalType
Indicates that an entity is associated with a specific type or classification of singing voice.
- 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_69ef3558cf8881909595ef89daf6e14a |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f6db3606808190a80c6e9f5da5b33e |
completed | May 3, 2026, 5:20 a.m. |
| PD | Predicate disambiguation | batch_69f6d82adfa481908a5e196d2e18c73f |
completed | May 3, 2026, 5:07 a.m. |
| PDg | Predicate description generation | batch_69f6db1bc348819097c844f76e2fa4fe |
completed | May 3, 2026, 5:20 a.m. |
Created at: April 27, 2026, 10:59 a.m.