Triple
T2307013
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ain't No Other Man |
E51862
|
entity |
| Predicate | hasNotableVocalPerformance |
P33230
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Ain't No Other Man, hasNotableVocalPerformance, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableVocalPerformance Context triple: [Ain't No Other Man, hasNotableVocalPerformance, yes]
-
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.
vocalPerformanceNotedFor
chosen
Indicates that a particular vocal performance is recognized or distinguished for a specific quality, feature, or characteristic.
-
C.
hasNotablePerformer
Indicates that an entity features or is associated with a performer who is particularly prominent, famous, or otherwise noteworthy.
-
D.
hasNotableMusicWork
Indicates that an entity is associated with a significant or well-known musical work, such as a composition, recording, or performance.
-
E.
hasNoLyrics
Indicates that the referenced musical work or audio track does not contain any sung or spoken lyrics.
- 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_69a88b0bb30c81908ded03b006d29387 |
completed | March 4, 2026, 7:42 p.m. |
| NER | Named-entity recognition | batch_69abce1f4f0c8190a714e4dcb8449f7e |
completed | March 7, 2026, 7:05 a.m. |
| PD | Predicate disambiguation | batch_69abc58ce2a081908ce2f0cadd92e9f8 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:49 p.m.