Triple
T34337806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Walk Like a Man |
E881200
|
entity |
| Predicate | vocalPerformanceFeature |
P29850
|
FINISHED |
| Object | falsetto vocals |
—
|
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: falsetto vocals | Statement: [Walk Like a Man, vocalPerformanceFeature, falsetto vocals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vocalPerformanceFeature Context triple: [Walk Like a Man, vocalPerformanceFeature, falsetto vocals]
-
A.
featuresVocal
Indicates that one entity includes or presents the vocal performance or voice of another entity.
-
B.
vocal
Indicates that an entity produces or is characterized by audible sounds, speech, or vocalizations.
-
C.
hasVocalPerformanceBy
Indicates that a vocal performance in a work or recording is performed by a specified person or group.
-
D.
featuresVocalPercussion
Indicates that the subject includes or makes use of vocal percussion (such as beatboxing or mouth-made rhythmic sounds) as part of its content or performance.
-
E.
vocalizationCharacteristic
chosen
Indicates how an entity’s vocal sounds are characterized, such as their quality, style, or distinctive acoustic features.
- 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_69f349ba96a08190b94887bae2d8ee49 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7886be6d8819095ec62e4f2cee858 |
completed | May 3, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69f7841440f48190b4346c08855951d2 |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 1, 2026, 1:58 a.m.