Triple
T33456612
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vovka Ashkenazy |
E856793
|
entity |
| Predicate | hasPerformedAs |
P194913
|
FINISHED |
| Object | soloist |
—
|
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: soloist | Statement: [Vovka Ashkenazy, hasPerformedAs, soloist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPerformedAs Context triple: [Vovka Ashkenazy, hasPerformedAs, soloist]
-
A.
hasPerformed
Indicates that an entity has carried out or completed a specific action, task, or activity.
-
B.
hasGivenPerformanceAt
Indicates that an entity has performed (e.g., a show, concert, or presentation) at a specific venue or event location.
-
C.
hasAct
Indicates that an entity performs, participates in, or is associated with a specific act or action.
-
D.
isPerformedAs
Indicates that an action or role is carried out in a particular manner, style, or capacity, often differing from its original or typical form.
-
E.
performedTo
Indicates that an action or performance is directed toward or carried out on a particular entity.
- 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_69f3497281a08190b4705de0b5f26ba7 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd8e5f7c4c8190ab8e2f2a7bb1bd79 |
completed | May 8, 2026, 7:18 a.m. |
| PD | Predicate disambiguation | batch_69fd8d8a16f08190b9e880901bfa44fe |
completed | May 8, 2026, 7:15 a.m. |
| PDg | Predicate description generation | batch_69fd8e5e9ca48190890a2caddc1f9f5c |
completed | May 8, 2026, 7:18 a.m. |
Created at: May 1, 2026, 1:37 a.m.