Triple
T27618421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suo-Gân |
E700501
|
entity |
| Predicate | hasVocalTexture |
P156193
|
FINISHED |
| Object | typically solo voice |
—
|
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: typically solo voice | Statement: [Suo-Gân, hasVocalTexture, typically solo voice]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVocalTexture Context triple: [Suo-Gân, hasVocalTexture, typically solo voice]
-
A.
hasVocals
Indicates that the subject includes or features vocal elements, such as singing or spoken voice, rather than being purely instrumental or non-vocal.
-
B.
hasVocalCharacter
chosen
Indicates that an entity possesses a particular vocal quality, style, or characteristic in its sound or voice.
-
C.
hasVocalForces
Indicates that an entity involves or employs vocal performers or vocal parts as a contributing force.
-
D.
hasMusicalVocalType
Indicates that an entity is associated with a specific type or classification of singing voice.
-
E.
hasVocalPerspective
Indicates that one entity expresses or frames content from the point of view or voice of another entity.
- 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_69ef6a4f1d9c8190b0705acda054368d |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f67f0488bc819089fbd2d2478158d3 |
completed | May 2, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69f67e3ed894819094c067c1ef624951 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 27, 2026, 2:13 p.m.