Triple
T4514942
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kreutzer Sonata |
E102131
|
entity |
| Predicate | typicalPerformanceMedium |
P27645
|
FINISHED |
| Object | violin and piano duo |
—
|
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: violin and piano duo | Statement: [Kreutzer Sonata, typicalPerformanceMedium, violin and piano duo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalPerformanceMedium Context triple: [Kreutzer Sonata, typicalPerformanceMedium, violin and piano duo]
-
A.
typicalPerformance
Indicates the usual or characteristic level at which an entity performs under normal conditions.
-
B.
performsMedium
Indicates that an entity carries out or executes an action, role, or function using a specified medium or means.
-
C.
typicalPerformanceMode
chosen
Indicates the usual or most common way in which an entity performs an action or operates.
-
D.
notablePerformanceMedium
Indicates the medium (such as film, stage, or television) in which an entity delivered a notable or distinguished performance.
-
E.
mediumAppearance
Indicates that an entity appears in or is featured within a particular medium (such as a work, format, or communication channel).
- 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_69bd43d6251c81909deecce3e6e9d69c |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd5725745c81908bb462ba9537ae14 |
completed | March 20, 2026, 2:18 p.m. |
| PD | Predicate disambiguation | batch_69bd521abea48190b3e758a1f98dd55e |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:02 p.m.