Triple
T34015811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King of Klezmer |
E872238
|
entity |
| Predicate | recognizesQuality |
P150173
|
FINISHED |
| Object | virtuosity |
—
|
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: virtuosity | Statement: [King of Klezmer, recognizesQuality, virtuosity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recognizesQuality Context triple: [King of Klezmer, recognizesQuality, virtuosity]
-
A.
recognisedQuality
chosen
Indicates that one entity acknowledges, identifies, or validates a particular quality or attribute present in another entity.
-
B.
supportsQuality
Indicates that one entity contributes to maintaining, enhancing, or ensuring the quality or standard of another entity or process.
-
C.
evokesQuality
Indicates that one entity elicits, suggests, or brings to mind a particular quality or characteristic associated with another.
-
D.
idealQuality
Indicates that one entity possesses a quality or attribute that is considered ideal, optimal, or most desirable in relation to another entity or context.
-
E.
showsQuality
Indicates that one entity exhibits, displays, or makes evident a particular quality or characteristic of another entity.
- 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_69f349a19ad88190ab586f010c804a8f |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd4129a8848190a5002150278ac689 |
completed | May 8, 2026, 1:49 a.m. |
| PD | Predicate disambiguation | batch_69fd3e0515ec8190937c7af71ebc3875 |
completed | May 8, 2026, 1:36 a.m. |
Created at: May 1, 2026, 1:51 a.m.