Triple
T11091921
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tamás Vásáry |
E262274
|
entity |
| Predicate | notablePerformanceType |
P54971
|
FINISHED |
| Object | solo piano recitals |
—
|
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: solo piano recitals | Statement: [Tamás Vásáry, notablePerformanceType, solo piano recitals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablePerformanceType Context triple: [Tamás Vásáry, notablePerformanceType, solo piano recitals]
-
A.
notablePrimaryPerformance
Indicates that an entity is recognized for a primary or leading performance in a work or event.
-
B.
notablePerformanceMedium
chosen
Indicates the medium (such as film, stage, or television) in which an entity delivered a notable or distinguished performance.
-
C.
notableAdaptationPerformance
Indicates that an entity is recognized for a significant performance in an adaptation of another work.
-
D.
notablePerformanceYear
Indicates the year in which an entity delivered a particularly significant or distinguished performance.
-
E.
hasNotablePerformanceIn
Indicates that an entity delivered a significant or distinguished performance within a specified work, event, or context.
- 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_69d6aa9a40d88190a373e2c7e48285db |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d799ec6564819097624195d0cd9093 |
completed | April 9, 2026, 12:22 p.m. |
| PD | Predicate disambiguation | batch_69d744185a5881909ba4cf151d1798ec |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:27 p.m.