Triple
T29026795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schumann’s symphonies |
E737613
|
entity |
| Predicate | typicalDurationRangePerWork |
P109104
|
FINISHED |
| Object | 30–45 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: 30–45 minutes | Statement: [Schumann’s symphonies, typicalDurationRangePerWork, 30–45 minutes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalDurationRangePerWork Context triple: [Schumann’s symphonies, typicalDurationRangePerWork, 30–45 minutes]
-
A.
typicalDurationMinutes
Indicates the usual or expected length of time, measured in minutes, that an event, activity, or process typically lasts.
-
B.
typicalRecordingDuration
Indicates the usual or standard length of time that something is recorded.
-
C.
typicalDurationDays
Indicates the usual or expected number of days that an associated event, process, or state typically lasts.
-
D.
hasTypicalPerformanceDuration
chosen
Indicates the usual or expected length of time that a performance or activity typically lasts.
-
E.
typicalMasterDuration
Indicates the usual or standard length of time for which a master (e.g., a primary or controlling entity) remains in effect or holds its role.
- 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_69f077ef00fc81909325f084ad37c035 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_6a016336c58081909c58c5772e6fb488 |
completed | May 11, 2026, 5:03 a.m. |
| PD | Predicate disambiguation | batch_6a0160f25d8081909a6aaa375e9850b0 |
completed | May 11, 2026, 4:54 a.m. |
Created at: April 28, 2026, 9:53 a.m.