Triple
T16856248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piano Concerto |
E409791
|
entity |
| Predicate | typicalNumberOfMovements |
P66232
|
FINISHED |
| Object | three movements |
—
|
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: three movements | Statement: [Piano Concerto, typicalNumberOfMovements, three movements]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalNumberOfMovements Context triple: [Piano Concerto, typicalNumberOfMovements, three movements]
-
A.
numberOfMovements
Indicates the total count of distinct movements or motion events associated with the given entity or context.
-
B.
typicalMovement
Indicates the usual or characteristic way in which an entity moves or is expected to move.
-
C.
typicalMovementCountPerSymphony
Indicates the usual number of movements that a symphony typically contains.
-
D.
movementNumber
Indicates the specific sequential position of a movement within a larger multi-movement work or performance.
-
E.
typicalMovementCountPerConcerto
chosen
Indicates the usual or standard number of movements that a concerto typically contains.
- 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.