Triple
T33537880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buddy Bolden |
E858984
|
entity |
| Predicate | hasNoSurvivingRecordings |
P203672
|
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: [Buddy Bolden, hasNoSurvivingRecordings, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNoSurvivingRecordings Context triple: [Buddy Bolden, hasNoSurvivingRecordings, true]
-
A.
hasNotableRecordingPeriod
Indicates that an entity is associated with a specific time span during which notable recording activity took place.
-
B.
hasNotableRecordingBy
Indicates that an entity (such as a work or composition) has a well-known or significant recording created or performed by a specified agent (such as an artist, ensemble, or label).
-
C.
hasWorkRecordingsOn
Indicates that an entity has associated work recordings stored on or linked to another entity (such as a medium, platform, or system).
-
D.
hasMultipleRecordings
Indicates that the same work, performance, or item exists in more than one distinct recorded version.
-
E.
hasRe-recording
Indicates that one recording is a new or updated version made again from the same original material or performance.
- 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_69f34978caf4819083f90eba4944d8e8 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a01c41dfe248190a68f4a262591b30f |
completed | May 11, 2026, 11:57 a.m. |
| PD | Predicate disambiguation | batch_6a01c375d14c8190a15bfa12623588a9 |
completed | May 11, 2026, 11:54 a.m. |
| PDg | Predicate description generation | batch_6a01c41d38608190923c5fd32a59b865 |
completed | May 11, 2026, 11:57 a.m. |
Created at: May 1, 2026, 1:39 a.m.