Triple
T36139495
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ray’s Rockhouse |
E1045253
|
entity |
| Predicate | vocalArrangementFor |
P37619
|
FINISHED |
| Object | vocal group |
—
|
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: vocal group | Statement: [Ray’s Rockhouse, vocalArrangementFor, vocal group]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vocalArrangementFor Context triple: [Ray’s Rockhouse, vocalArrangementFor, vocal group]
-
A.
vocalArrangement
chosen
Indicates the specific way vocal parts or voices are organized, structured, and combined within a musical work or performance.
-
B.
musicalArrangement
Indicates that one entity is an arrangement or adaptation of another musical work.
-
C.
vocalArrangementComparedToOriginal
Indicates how the vocal arrangement in a given version differs from or relates to the vocal arrangement in the original version.
-
D.
vocalAccompaniment
Indicates that one entity provides vocal support or accompaniment to another entity’s primary performance or action.
-
E.
vocalForm
Indicates the specific vocal or phonetic form in which something (such as a word, sound, or utterance) is expressed.
- 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_69f76e36a4508190b5bfc8f594272a4c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c475c58c8190a883554231e88c88 |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 3, 2026, 4:08 p.m.