Triple
T5453419
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Symphonie fantastique |
E122421
|
entity |
| Predicate | keyOfFirstMovement |
P40256
|
FINISHED |
| Object | C minor |
—
|
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: C minor | Statement: [Symphonie fantastique, keyOfFirstMovement, C minor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyOfFirstMovement Context triple: [Symphonie fantastique, keyOfFirstMovement, C minor]
-
A.
firstMovementKey
chosen
Indicates the musical key in which the first movement of a multi-movement work is composed.
-
B.
movement1Key
Indicates a relationship where an entity’s primary or defining movement action or motion pattern is specified or referenced.
-
C.
finalMovementKey
Indicates that one movement in a sequence is designated as the last or concluding movement, often used as a key or reference to the final step in a process or animation.
-
D.
thirdMovementKey
Indicates the musical key in which the third movement of a multi-movement work is composed or performed.
-
E.
keyPosition
Indicates the specific location or placement of a key within a defined space or system.
- 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_69bd46424248819085282ddf50a565f3 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd95be329c81908783420cf81b6af5 |
completed | March 20, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_69bd919e8d18819098c4af6a015e5cc2 |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:08 p.m.