Triple
T8469697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kreisleriana, Op. 16 |
E200248
|
entity |
| Predicate | targetPerformer |
P20624
|
FINISHED |
| Object | concert pianists |
—
|
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: concert pianists | Statement: [Kreisleriana, Op. 16, targetPerformer, concert pianists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetPerformer Context triple: [Kreisleriana, Op. 16, targetPerformer, concert pianists]
-
A.
coPerformer
Indicates that two or more entities jointly perform the same act or participate together in the same performance.
-
B.
performerType
chosen
Indicates the role or category of performer responsible for carrying out an action or participating in an event.
-
C.
performerOn
Indicates that an entity serves as the performer or executing agent of an action, event, or work associated with another entity.
-
D.
performedBy
Indicates that an action, task, or event is carried out or executed by a specified agent or entity.
-
E.
associatedWithPerformer
Indicates a relationship in which something (such as a work, event, or role) is connected or linked to a specific performer.
- 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_69ca831a4f348190bfdd09250e86ae35 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe4d5dd088190a79050417f527f14 |
completed | March 31, 2026, 3:14 p.m. |
| PD | Predicate disambiguation | batch_69cbd10072cc819084be1ed9ac7ebe9d |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:11 p.m.