Triple
T34637135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blind Alfred Reed |
E889456
|
entity |
| Predicate | hasRecordingIn |
—
|
GENERATED |
| Object | Bristol Sessions |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRecordingIn Context triple: [Blind Alfred Reed, hasRecordingIn, Bristol Sessions]
-
A.
hasRecordingWith
Indicates that one entity is associated with or includes a particular recording as part of its content or representation.
-
B.
hasLiveRecordingFrom
Indicates that a live recording was made of something (e.g., a work, performance, or event) at or from a specified source, venue, or occasion.
-
C.
hasWorkRecordingsOn
chosen
Indicates that an entity has associated work recordings stored on or linked to another entity (such as a medium, platform, or system).
-
D.
hasRe-recording
Indicates that one recording is a new or updated version made again from the same original material or performance.
-
E.
hasRecordingLegacy
Indicates that an entity is associated with a historical or prior version of a recording, capturing its legacy or earlier state.
- F. None of above.
Provenance (1 batch)
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_69f349d724848190b63ad3407e0006d9 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 2:04 a.m.