Triple
T36858023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sweet Sue and Her Society Syncopators |
E910849
|
entity |
| Predicate | includesVocalist |
P68721
|
FINISHED |
| Object | Sugar Kane Kowalczyk |
E264842
|
NE 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: Sugar Kane Kowalczyk | Statement: [Sweet Sue and Her Society Syncopators, includesVocalist, Sugar Kane Kowalczyk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesVocalist Context triple: [Sweet Sue and Her Society Syncopators, includesVocalist, Sugar Kane Kowalczyk]
-
A.
vocalistIn
chosen
Indicates that a person serves as a vocalist (singer) in a particular musical group, band, or ensemble.
-
B.
hasVerseVocalist
Indicates that a person performs the vocal part specifically in the verse section of a musical work or recording.
-
C.
hasVocalPerformanceBy
Indicates that a vocal performance in a work or recording is performed by a specified person or group.
-
D.
vocalistOnOriginalRecording
Indicates that the subject served as the vocalist on the original recording of the work or track.
-
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 (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_69f76e8033d48190a59274f86f13be48 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3e2c226f6881908738a1cf6f394f66 |
completed | June 26, 2026, 7:37 a.m. |
| PD | Predicate disambiguation | batch_6a037a0e039481908a4a2666f76c5363 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:13 p.m.