Triple
T10366947
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | As If to Nothing |
E244276
|
entity |
| Predicate | hasGuestVocalists |
P93602
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [As If to Nothing, hasGuestVocalists, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGuestVocalists Context triple: [As If to Nothing, hasGuestVocalists, true]
-
A.
recordingArtistOfGuestVocalist
Indicates that an artist is the primary recording artist on a work that features another artist as a guest vocalist.
-
B.
guestVocalistIsFrontmanOf
Indicates that the guest vocalist performing on a work is also the lead singer (frontman) of the referenced band or primary musical act.
-
C.
hasGuestVerseBy
Indicates that a work (such as a song or track) includes a guest verse performed by a specified artist.
-
D.
hasNotableGuest
Indicates that an entity has a guest who is distinguished, prominent, or otherwise noteworthy in some significant way.
-
E.
hasBackingVocals
Indicates that one musical performance, track, or part includes supporting vocal contributions accompanying a primary vocal line.
- F. None of above. chosen
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_69d381b3e328819094b23b8edcd29b5a |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e96fd6f081908f630a16106996d9 |
completed | April 7, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69d4dface5508190a7b42f01ad0a19a2 |
completed | April 7, 2026, 10:42 a.m. |
| PDg | Predicate description generation | batch_69d4e944fac4819093b0312aa0efd729 |
completed | April 7, 2026, 11:23 a.m. |
Created at: April 6, 2026, noon