Triple
T32762300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Bonnie and Clyde Theme |
E837789
|
entity |
| Predicate | notableCellist |
P146501
|
FINISHED |
| Object | Yo-Yo Ma |
E5117
|
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: Yo-Yo Ma | Statement: [The Bonnie and Clyde Theme, notableCellist, Yo-Yo Ma]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableCellist Context triple: [The Bonnie and Clyde Theme, notableCellist, Yo-Yo Ma]
-
A.
notableCellistsAssociated
chosen
Indicates that there is a notable cellist who is associated with the given entity, such as through collaboration, membership, or significant involvement.
-
B.
notableMusician
Indicates that the subject is a musician who is widely recognized or distinguished for their musical work or impact.
-
C.
notableKeyboardist
Indicates that the subject is a keyboard player who is widely recognized or distinguished for their skill, influence, or prominence.
-
D.
notableLuthier
Indicates that a person is recognized as a distinguished or prominent maker of stringed musical instruments (a luthier).
-
E.
notableArtist
Indicates that the subject is an artist who is widely recognized or distinguished for their work.
- 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_69f34939857c8190aa9970c51feec1eb |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a34c667661c8190a2d7d9e17ef68e91 |
completed | June 19, 2026, 4:32 a.m. |
| PD | Predicate disambiguation | batch_6a0379f0cbe481909b4b8fc6cbe297f0 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:13 a.m.