Triple
T8857153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Symphony No. 5 in C-sharp minor |
E210785
|
entity |
| Predicate | openingMovementType |
P83469
|
FINISHED |
| Object | funeral march |
—
|
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: funeral march | Statement: [Symphony No. 5 in C-sharp minor, openingMovementType, funeral march]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openingMovementType Context triple: [Symphony No. 5 in C-sharp minor, openingMovementType, funeral march]
-
A.
hasOpeningMovement
chosen
Indicates that a work, performance, or sequence includes a distinct initial movement or section that begins the overall piece.
-
B.
openingSequenceType
Indicates the specific kind or category of an opening sequence associated with an entity or event.
-
C.
openingTo
Indicates that one entity serves as an entrance, access point, or passage leading into or toward another entity.
-
D.
openingDetail
Indicates the specific manner, context, or characteristics of how an opening (such as a beginning, start, or initial access point) occurs or is carried out between entities.
-
E.
openingWorkOf
Indicates that one work serves as the first or introductory piece in relation to another work, such as the opening item in a sequence or collection.
- 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_69ca838bbddc8190ab546d737e5d350f |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc60e259248190abd334bbfcdcb955 |
completed | April 1, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69cc5c279ea481908c71756f694b66bf |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:50 p.m.