Triple
T16856251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piano Concerto |
E409791
|
entity |
| Predicate | commonThirdMovementCharacter |
P99498
|
FINISHED |
| Object | fast movement |
—
|
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 movement | Statement: [Piano Concerto, commonThirdMovementCharacter, fast movement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonThirdMovementCharacter Context triple: [Piano Concerto, commonThirdMovementCharacter, fast movement]
-
A.
thirdMovementType
Indicates the specific type or category of the third movement within a larger sequence or structure of movements.
-
B.
characterOfThirdMovement
chosen
Indicates that something specifies the musical or expressive character of the third movement of a larger work.
-
C.
thirdMovementKey
Indicates the musical key in which the third movement of a multi-movement work is composed or performed.
-
D.
movement3Key
Indicates a three-part or third-level categorization of how an entity moves or changes location relative to another entity or reference point.
-
E.
thirdWord
Indicates that one entity is the third word in sequence within another entity (such as a text or phrase).
- 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_69d88395e6c88190b22730f335107c14 |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b37d69a08190af18b421066f44f1 |
completed | April 18, 2026, 4:38 p.m. |
| PD | Predicate disambiguation | batch_69e32b8cbb048190878a259cc5be960e |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:24 a.m.