Triple
T19665928
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Live at Massey Hall 1971 |
E472197
|
entity |
| Predicate | isSoloPerformance |
P136878
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Live at Massey Hall 1971, isSoloPerformance, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSoloPerformance Context triple: [Live at Massey Hall 1971, isSoloPerformance, true]
-
A.
soloist
Indicates that an entity performs or appears alone as the primary featured performer in an artistic or musical context.
-
B.
isSoloPartFor
Indicates that something functions as an individual or standalone component within a larger whole or composition.
-
C.
hasNotableSoloFor
Indicates that an individual is recognized for performing a prominent or distinguished solo part within a larger work or performance associated with another entity.
-
D.
featuresSoloPerformancesBy
Indicates that the subject includes or showcases solo performances carried out by the specified performer or performers.
-
E.
hasImprovisedSoloBy
Indicates that an improvised solo performance is attributed to or performed by a specific entity.
- 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_69d8e514f2e08190ba70a4449519d218 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6416857c88190acb3adbf3e585fe5 |
completed | April 20, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_69e514e941008190898d978d7bde91e4 |
completed | April 19, 2026, 5:46 p.m. |
| PDg | Predicate description generation | batch_69e51a23300c8190988552491d9783d7 |
completed | April 19, 2026, 6:08 p.m. |
Created at: April 10, 2026, 1:45 p.m.