Triple
T35620535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ooh Carla, Ooh Otis |
E1029299
|
entity |
| Predicate | hasCollaboratingVocalist |
P54926
|
FINISHED |
| Object | Otis Redding |
E53220
|
NE 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: Otis Redding | Statement: [Ooh Carla, Ooh Otis, hasCollaboratingVocalist, Otis Redding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCollaboratingVocalist Context triple: [Ooh Carla, Ooh Otis, hasCollaboratingVocalist, Otis Redding]
-
A.
hasOutroVocalist
Indicates that an entity (such as a song or track) features a vocalist specifically during its outro section.
-
B.
hasNotableBackingVocalist
Indicates that an entity (typically a song or recording) features a backing vocalist who is particularly prominent, famous, or otherwise noteworthy.
-
C.
hasVerseVocalist
Indicates that a person performs the vocal part specifically in the verse section of a musical work or recording.
-
D.
featuresVocalCollaborations
chosen
Indicates that the work includes vocal performances by multiple distinct artists collaborating together.
-
E.
hasBackingVocals
Indicates that one musical performance, track, or part includes supporting vocal contributions accompanying a primary vocal line.
- F. None of above.
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_69f76e0709408190bbe322bf1707ef6b |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a387cfa4c988190b575f6b46cc57a1c |
completed | June 22, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_6a037a04d8348190a4819666eab42c9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:05 p.m.