Triple
T37356941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sonata No. 1 in G minor, BWV 1001 |
E927478
|
entity |
| Predicate | hasFugueMovement |
P187764
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Sonata No. 1 in G minor, BWV 1001, hasFugueMovement, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFugueMovement Context triple: [Sonata No. 1 in G minor, BWV 1001, hasFugueMovement, true]
-
A.
fugueMovement
chosen
Indicates a musical relationship where a section or movement is structured as a fugue, featuring imitative counterpoint among independent voices.
-
B.
hasFugue
Indicates that an entity possesses or is characterized by a fugue, such as a fugue state, episode, or condition.
-
C.
hasFinaleMovement
Indicates that one entity (typically a musical work or performance) includes another entity as its concluding or final movement.
-
D.
hasScherzoMovement
Indicates that a musical work includes a scherzo as one of its movements.
-
E.
fugueLength
Indicates the duration or extent of a fugue, typically measured in time or number of measures.
- 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_69f76eb701788190b40824bc4594d985 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb9e1845e881908d19158440cf3b87 |
completed | May 6, 2026, 8:01 p.m. |
| PD | Predicate disambiguation | batch_69fb8d08d6988190a00794ac26078348 |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:16 p.m.