Triple
T28489984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Rhumba |
E720935
|
entity |
| Predicate | hasKeyPerformerOnNotableRecording |
P1152
|
FINISHED |
| Object | Miles Davis |
—
|
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: Miles Davis | Statement: [New Rhumba, hasKeyPerformerOnNotableRecording, Miles Davis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeyPerformerOnNotableRecording Context triple: [New Rhumba, hasKeyPerformerOnNotableRecording, Miles Davis]
-
A.
hasKeyPerformerOnRecording
Indicates that a particular performer is a principal or featured contributor on a specific recording.
-
B.
hasNotableRecordingBy
chosen
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.
hasNotablePerformer
Indicates that an entity features or is associated with a performer who is particularly prominent, famous, or otherwise noteworthy.
-
D.
hasPerformerGivenName
Indicates that a performer is associated with a specific given (first) name.
-
E.
keyInManyPerformances
Indicates that the entity serves as a central or essential element in numerous performances or events.
- 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_69f01a5a47148190b0a7e111bc432e0a |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f6b903538481909cffcb6cc1cc0e70 |
completed | May 3, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69f6b626120c819097c9ad04487570d7 |
completed | May 3, 2026, 2:42 a.m. |
Created at: April 28, 2026, 3 a.m.