Triple
T33763340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Future World |
E865168
|
entity |
| Predicate | hasVocalistOnOriginalRecording |
P160279
|
FINISHED |
| Object | Michael Kiske |
—
|
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 Kiske | Statement: [Future World, hasVocalistOnOriginalRecording, Michael Kiske]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVocalistOnOriginalRecording Context triple: [Future World, hasVocalistOnOriginalRecording, Michael Kiske]
-
A.
vocalistOnOriginalRecording
chosen
Indicates that the subject served as the vocalist on the original recording of the work or track.
-
B.
usesOriginalVocalsFrom
Indicates that one work incorporates the original, unaltered vocal recordings from another work.
-
C.
hasVerseVocalist
Indicates that a person performs the vocal part specifically in the verse section of a musical work or recording.
-
D.
hasVocalPerformanceBy
Indicates that a vocal performance in a work or recording is performed by a specified person or group.
-
E.
hasOutroVocalist
Indicates that an entity (such as a song or track) features a vocalist specifically during its outro section.
- 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_69f3498d3b748190aa3c4006c1f32f38 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7516d5b4081908588a6feb541f355 |
completed | May 3, 2026, 1:45 p.m. |
| PD | Predicate disambiguation | batch_69f74d40ebb081909daf60623e38f41d |
completed | May 3, 2026, 1:27 p.m. |
Created at: May 1, 2026, 1:45 a.m.