Triple
T25806519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lovedrive |
E649981
|
entity |
| Predicate | guestGuitarPerformanceBy |
P159290
|
FINISHED |
| Object | Michael Schenker |
—
|
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: Michael Schenker | Statement: [Lovedrive, guestGuitarPerformanceBy, Michael Schenker]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: guestGuitarPerformanceBy Context triple: [Lovedrive, guestGuitarPerformanceBy, Michael Schenker]
-
A.
performsMusicIn
Indicates that an entity presents or plays music within a particular venue, event, or context.
-
B.
performsMusicFrom
Indicates that one entity presents or executes a musical work that originates from or was created by another entity.
-
C.
providedPianoPerformancesFor
Indicates that one entity supplied or delivered piano performances for the benefit, use, or event of another entity.
-
D.
guitarInFilmPerformanceBy
Indicates that a guitar is used or featured in a musical performance within a film, and specifies the performer responsible for that guitar performance.
-
E.
drumPerformanceBy
Indicates that a drum performance is executed or carried out by a specified agent or performer.
- 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_69e7ab35d264819095367f7e80c983ff |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f5ffd08e288190bf9b7e3aa847725a |
completed | May 2, 2026, 1:44 p.m. |
| PD | Predicate disambiguation | batch_69f4938b960081909b53c074a3e0c7c2 |
completed | May 1, 2026, 11:50 a.m. |
| PDg | Predicate description generation | batch_69f497b8abb88190bb672cf6907c4b8d |
completed | May 1, 2026, 12:08 p.m. |
Created at: April 22, 2026, 7:04 a.m.