Triple
T6202619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trio Sonatas Op. 3 |
E138670
|
entity |
| Predicate | typicalMovementStructure |
P45058
|
FINISHED |
| Object | slow-fast-slow-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: slow-fast-slow-fast | Statement: [Trio Sonatas Op. 3, typicalMovementStructure, slow-fast-slow-fast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalMovementStructure Context triple: [Trio Sonatas Op. 3, typicalMovementStructure, slow-fast-slow-fast]
-
A.
hasMovementStructure
chosen
Indicates that one entity possesses or is characterized by a particular structure or pattern of movement.
-
B.
movementType
Indicates the manner or mode in which an entity moves or is moved from one place or state to another.
-
C.
actStructure
Indicates a structural or organizational relationship that defines how an action or activity is arranged, composed, or internally organized.
-
D.
typicalSegmentType
Indicates that something is classified as belonging to a usual or characteristic type of segment within a broader structure or sequence.
-
E.
movementCharacteristic
Indicates how an entity moves or behaves in motion, such as its style, pattern, or quality of movement.
- 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_69c008acbea48190991c6b834bb45d65 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0626a32908190a3332008aee2e4a9 |
completed | March 22, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69c055fbce1081908805fd12e242ab96 |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:20 p.m.