Triple
T21937926
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Symphony No. 7 in E major |
E541741
|
entity |
| Predicate | keyOfMovement |
P39542
|
FINISHED |
| Object | I. Allegro moderato in E major |
—
|
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: I. Allegro moderato in E major | Statement: [Symphony No. 7 in E major, keyOfMovement, I. Allegro moderato in E major]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyOfMovement Context triple: [Symphony No. 7 in E major, keyOfMovement, I. Allegro moderato in E major]
-
A.
keyOfMovement7
Indicates a specific key or control input that triggers or corresponds to the seventh defined type of movement in a system.
-
B.
keyMovement
Indicates the movement or transfer of a key from one location, state, or holder to another.
-
C.
movement1Key
Indicates a relationship where an entity’s primary or defining movement action or motion pattern is specified or referenced.
-
D.
movement2Key
chosen
Indicates a mapping or correspondence between a specific movement and its associated key (such as a musical key, identifier, or control).
-
E.
movement7Key
Indicates a relationship where an entity’s movement is characterized by or associated with a specific key, code, or identifier labeled as "7".
- 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_69e0c47e2e5c81909a7f74ce3de50911 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f1241e35bc81909eb3225d5cd97b92 |
completed | April 28, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69e6f5efc208819091ed2cf6841fa600 |
completed | April 21, 2026, 3:58 a.m. |
Created at: April 16, 2026, 7:55 p.m.