Triple
T34637135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blind Alfred Reed |
E889456
|
entity |
| Predicate | hasRecordingIn |
P155529
|
FINISHED |
| Object | Bristol Sessions |
E2105099
|
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: Bristol Sessions | Statement: [Blind Alfred Reed, hasRecordingIn, Bristol Sessions]
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 (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_69f349d724848190b63ad3407e0006d9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a375bd004a081908a03f177d65d5c22 |
completed | June 21, 2026, 3:34 a.m. |
| PD | Predicate disambiguation | batch_6a0379fd7aac8190873077e63873aa72 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 2:04 a.m.