Triple
T8999844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Symphony No. 25 in G minor |
E215013
|
entity |
| Predicate | timeSignatureFirstMovement |
P85603
|
FINISHED |
| Object | common time |
—
|
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: common time | Statement: [Symphony No. 25 in G minor, timeSignatureFirstMovement, common time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeSignatureFirstMovement Context triple: [Symphony No. 25 in G minor, timeSignatureFirstMovement, common time]
-
A.
firstMovementTempoMarking
Indicates the tempo marking associated with the first movement of a work or composition.
-
B.
tonalityOfFirstMovement
Indicates the key or tonal center in which the first movement of a musical work is composed.
-
C.
timeSignatureChange
Indicates a change from one musical time signature to another within a piece or passage.
-
D.
firstMovementForm
Indicates that the subject is in the form or configuration it has during its first movement or initial phase of motion.
-
E.
firstMovement
Indicates that an entity represents the initial or earliest movement, action, or motion in a sequence of movements.
- F. None of above. chosen
Provenance (4 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_69ca83a12d648190b1e4fe11e8a31890 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc68e3b1f48190bbeafbce363fff53 |
completed | April 1, 2026, 12:37 a.m. |
| PD | Predicate disambiguation | batch_69cc5edd6cb48190b4fc6d6ca0418056 |
completed | March 31, 2026, 11:55 p.m. |
| PDg | Predicate description generation | batch_69cc5f6dec4081909379bd57c02a5710 |
completed | March 31, 2026, 11:57 p.m. |
Created at: March 30, 2026, 7:05 p.m.