Triple
T32324977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | My Love (guitar solo, with Wings) |
E825882
|
entity |
| Predicate | backingBandOnRecording |
P28442
|
FINISHED |
| Object | Wings |
—
|
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: Wings | Statement: [My Love (guitar solo, with Wings), backingBandOnRecording, Wings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: backingBandOnRecording Context triple: [My Love (guitar solo, with Wings), backingBandOnRecording, Wings]
-
A.
hasBackingBand
chosen
Indicates that an artist or performer is supported musically by a specific band that plays instruments or accompaniment for them.
-
B.
bandMemberOnRecording
Indicates that a person is a member of a band who performed on a specific recording.
-
C.
recordedByBandMemberOf
Indicates that a recording was made by an individual who is a member of a specified band.
-
D.
hasBackingMusician
Indicates that one entity serves as a supporting or accompanying musician for another entity, typically in a performance or recording context.
-
E.
backedArtist
Indicates that one entity has provided support, endorsement, or resources to an artist entity.
- 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_69f34912d0c48190bba75770660320e9 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bde7cd8481908d3128d089c86c14 |
completed | May 3, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69f6b633e0c88190a727bb7d2751e2d5 |
completed | May 3, 2026, 2:43 a.m. |
Created at: May 1, 2026, 12:47 a.m.