Triple
T23275001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tarkus |
E588392
|
entity |
| Predicate | mainPerformerBassAndVocals |
P15279
|
FINISHED |
| Object | Greg Lake |
—
|
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: Greg Lake | Statement: [Tarkus, mainPerformerBassAndVocals, Greg Lake]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainPerformerBassAndVocals Context triple: [Tarkus, mainPerformerBassAndVocals, Greg Lake]
-
A.
bassistOnMostRecordings
Indicates that the referenced person serves as the bass player on the majority of a specified artist’s or group’s recordings.
-
B.
hasBassist
chosen
Indicates that an entity (typically a musical group or band) has another entity serving in the role of its bassist.
-
C.
rhythmSectionPerformer
Indicates that a performer participates specifically as a member of the rhythm section within a musical ensemble.
-
D.
houseBandMember
Indicates that a person is a member of a house band, typically performing regularly as part of that resident musical group.
-
E.
usesBassGuitar
Indicates that one entity plays or employs a bass guitar in relation to another entity or context.
- 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_69e25d148adc819088efbf42672604e9 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f195768b1c8190ae7cbf8c316ae4dd |
completed | April 29, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69effcecabd88190856fb6e1d993e4dd |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:47 p.m.