Triple
T9175629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Symphony No. 40 in G minor |
E220191
|
entity |
| Predicate | thirdMovementForm |
P83105
|
FINISHED |
| Object | minuet and trio |
—
|
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: minuet and trio | Statement: [Symphony No. 40 in G minor, thirdMovementForm, minuet and trio]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: thirdMovementForm Context triple: [Symphony No. 40 in G minor, thirdMovementForm, minuet and trio]
-
A.
thirdMovementType
Indicates the specific type or category of the third movement within a larger sequence or structure of movements.
-
B.
thirdMovementKey
Indicates the musical key in which the third movement of a multi-movement work is composed or performed.
-
C.
secondMovementForm
Indicates that an entity is in the form or structure of the second movement within a larger multi-movement work or sequence.
-
D.
typicalFormOfThirdMovement
chosen
Indicates the characteristic or standard structural pattern commonly used for the third movement within a larger multi-movement work.
-
E.
thirdStageType
Indicates the specific kind or classification of a third stage within a multi-stage process or structure.
- 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_69ca83e589948190ac9907819db11ddf |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccbfa496548190a096969eebf732f3 |
completed | April 1, 2026, 6:48 a.m. |
| PD | Predicate disambiguation | batch_69cc660761d88190ab6134b43b376964 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:23 p.m.