Triple
T9430700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tchaikovsky's Third Symphony |
E227366
|
entity |
| Predicate | movementCountType |
P32659
|
FINISHED |
| Object | five-movement structure |
—
|
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: five-movement structure | Statement: [Tchaikovsky's Third Symphony, movementCountType, five-movement structure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: movementCountType Context triple: [Tchaikovsky's Third Symphony, movementCountType, five-movement structure]
-
A.
movementCount
Indicates the number of times a movement or relocation action has occurred between the related entities.
-
B.
movementNumber
Indicates the specific sequential position of a movement within a larger multi-movement work or performance.
-
C.
numberOfMovements
chosen
Indicates the total count of distinct movements or motion events associated with the given entity or context.
-
D.
movementType
Indicates the manner or mode in which an entity moves or is moved from one place or state to another.
-
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_69ca8436ba308190903e470776d2d893 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd7e5ed7408190beda5fb078e9345a |
completed | April 1, 2026, 8:21 p.m. |
| PD | Predicate disambiguation | batch_69cca55548488190b171ae695a3212de |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:49 p.m.