Triple
T8729197
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Symphony No. 1 in D major |
E207210
|
entity |
| Predicate | originalNumberOfMovements |
P32659
|
FINISHED |
| Object | 5 |
—
|
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: 5 | Statement: [Symphony No. 1 in D major, originalNumberOfMovements, 5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalNumberOfMovements Context triple: [Symphony No. 1 in D major, originalNumberOfMovements, 5]
-
A.
numberOfMovements
chosen
Indicates the total count of distinct movements or motion events associated with the given entity or context.
-
B.
movementNumber
Indicates the specific sequential position of a movement within a larger multi-movement work or performance.
-
C.
movementCount
Indicates the number of times a movement or relocation action has occurred between the related entities.
-
D.
numberOfTurns
Indicates the total count of discrete turns or rotations involved in an interaction, process, or motion.
-
E.
typicalMovementCountPerConcerto
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_69ca8358e4008190898471a59b96c301 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5d19fdc88190860e0c9c93ab79ce |
completed | March 31, 2026, 11:47 p.m. |
| PD | Predicate disambiguation | batch_69cc457093188190959287a6458651c6 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:37 p.m.