Triple
T37611441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clarinet Sonatas, Op. 120 |
E935793
|
entity |
| Predicate | typicalPerformanceDurationOfSet |
P109104
|
FINISHED |
| Object | approximately 45–50 minutes |
—
|
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: approximately 45–50 minutes | Statement: [Clarinet Sonatas, Op. 120, typicalPerformanceDurationOfSet, approximately 45–50 minutes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalPerformanceDurationOfSet Context triple: [Clarinet Sonatas, Op. 120, typicalPerformanceDurationOfSet, approximately 45–50 minutes]
-
A.
hasTypicalPerformanceDuration
chosen
Indicates the usual or expected length of time that a performance or activity typically lasts.
-
B.
typicalRecordingDuration
Indicates the usual or standard length of time that something is recorded.
-
C.
typicalDurationOfRecital
Indicates the usual length of time that a recital event is expected to last.
-
D.
typicalDurationMinutes
Indicates the usual or expected length of time, measured in minutes, that an event, activity, or process typically lasts.
-
E.
typicalBoutLength
Indicates the usual or characteristic duration of a single bout or episode of an activity or behavior.
- 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_69f76ed0a85481909254a8a89090c826 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1553e08190bb7424c448cb1f33 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:18 p.m.