Triple
T33916419
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gwen Dickey |
E869468
|
entity |
| Predicate | providedVocalsForSong |
P168042
|
FINISHED |
| Object | Car Wash |
—
|
NE NERFINISHED |
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: Car Wash | Statement: [Gwen Dickey, providedVocalsForSong, Car Wash]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: providedVocalsForSong Context triple: [Gwen Dickey, providedVocalsForSong, Car Wash]
-
A.
providedVocalPerformanceFor
chosen
Indicates that one entity delivered or contributed a vocal performance in support of, or as part of, another entity’s work, event, or production.
-
B.
hasVocals
Indicates that the subject includes or features vocal elements, such as singing or spoken voice, rather than being purely instrumental or non-vocal.
-
C.
hasBackingVocals
Indicates that one musical performance, track, or part includes supporting vocal contributions accompanying a primary vocal line.
-
D.
vocalAccompaniment
Indicates that one entity provides vocal support or accompaniment to another entity’s primary performance or action.
-
E.
hasVocalPerformanceBy
Indicates that a vocal performance in a work or recording is performed by a specified person or group.
- 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_69f3499869bc8190b6c33a81686af226 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fe2f078c24819082ba396b56f02808 |
completed | May 8, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69fe228fe1988190baf3bb34897f3dbe |
completed | May 8, 2026, 5:51 p.m. |
Created at: May 1, 2026, 1:48 a.m.