Triple
T31763355
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Felix Mendelssohn's symphonies |
E810739
|
entity |
| Predicate | commonTempoPlan |
P195906
|
FINISHED |
| Object | fast–slow–dance–fast |
—
|
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: fast–slow–dance–fast | Statement: [Felix Mendelssohn's symphonies, commonTempoPlan, fast–slow–dance–fast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonTempoPlan Context triple: [Felix Mendelssohn's symphonies, commonTempoPlan, fast–slow–dance–fast]
-
A.
commonTempo
Indicates that two or more musical entities share the same tempo or rate of beats per minute.
-
B.
musicalTempo
Indicates the speed or pace at which a piece of music is performed or intended to be performed.
-
C.
movement6Tempo
Indicates the tempo or speed at which the sixth movement of a work is performed or proceeds.
-
D.
movement7Tempo
Indicates the tempo at which the seventh movement of a work is performed or intended to be played.
-
E.
typicalTempoControl
Indicates that one entity serves as the usual or standard means by which the tempo of another entity (such as a process or activity) is regulated or controlled.
- 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_69f348e463e08190b902d4819195e1f0 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fdee770af48190aca2670db50f8b49 |
completed | May 8, 2026, 2:08 p.m. |
| PD | Predicate disambiguation | batch_69fdecec98a08190a357d816dc2a6dbe |
completed | May 8, 2026, 2:02 p.m. |
| PDg | Predicate description generation | batch_69fdee75d1408190bba58a9cef200a54 |
completed | May 8, 2026, 2:08 p.m. |
Created at: April 30, 2026, 11:31 p.m.