Triple
T31570570
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Symphony No. 3 |
E805546
|
entity |
| Predicate | hasTypicalDurationRange |
P109104
|
FINISHED |
| Object | 30–60 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–60 minutes | Statement: [Symphony No. 3, hasTypicalDurationRange, 30–60 minutes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalDurationRange Context triple: [Symphony No. 3, hasTypicalDurationRange, 30–60 minutes]
-
A.
hasTypicalPerformanceDuration
chosen
Indicates the usual or expected length of time that a performance or activity typically lasts.
-
B.
hasDurationCharacteristic
Indicates that something possesses a specific temporal property, such as length, span, or persistence over time.
-
C.
hasTypicalUseTime
Indicates the usual or expected duration or time period during which something is commonly used or in operation.
-
D.
typicalPeriodRange
Indicates the usual or most commonly observed range of time intervals associated with an event, process, or state.
-
E.
hasOfficialDuration
Indicates the formally defined length of time associated with an event, process, or entity.
- 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_69f348d2ee94819091918d1789398c29 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fe96c2647c819082989f11e1ae3d35 |
completed | May 9, 2026, 2:06 a.m. |
| PD | Predicate disambiguation | batch_69fe928615448190af939e5a94be55bb |
completed | May 9, 2026, 1:48 a.m. |
Created at: April 30, 2026, 10:19 p.m.