Triple
T2011555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Symphony No. 3 in D major, Op. 29 |
E43696
|
entity |
| Predicate | typicalPerformanceDuration |
P21649
|
FINISHED |
| Object | approximately 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: approximately 45 minutes | Statement: [Symphony No. 3 in D major, Op. 29, typicalPerformanceDuration, approximately 45 minutes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalPerformanceDuration Context triple: [Symphony No. 3 in D major, Op. 29, typicalPerformanceDuration, approximately 45 minutes]
-
A.
typicalRecordingDuration
Indicates the usual or standard length of time that something is recorded.
-
B.
typicalDurationDays
Indicates the usual or expected number of days that an associated event, process, or state typically lasts.
-
C.
typicalPerformanceMode
Indicates the usual or most common way in which an entity performs an action or operates.
-
D.
typicalRuntimeRange
Indicates the usual lower and upper bounds of time typically required for an entity to run or complete its operation.
-
E.
showDuration
chosen
Indicates the length of time for which something is shown, displayed, or performed.
- 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_69a88716e9f08190946313fdc949e3cf |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb8b150a8819096c919465fd91ab5 |
completed | March 7, 2026, 5:33 a.m. |
| PD | Predicate disambiguation | batch_69abb7a03a1c81909ad50d56667db2d5 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:37 p.m.