Triple
T8857105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Symphony No. 4 in G major |
E210784
|
entity |
| Predicate | finaleFeatures |
P80690
|
FINISHED |
| Object | soprano solo |
—
|
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: soprano solo | Statement: [Symphony No. 4 in G major, finaleFeatures, soprano solo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finaleFeatures Context triple: [Symphony No. 4 in G major, finaleFeatures, soprano solo]
-
A.
featuresIn
chosen
Indicates that an entity appears or plays a role within another entity, such as a person or element being included in a work, event, or context.
-
B.
originalFinale
Indicates that something serves as the initial or authentic concluding part or ending of another work, event, or sequence.
-
C.
hasFinaleMovement
Indicates that one entity (typically a musical work or performance) includes another entity as its concluding or final movement.
-
D.
finaleCharacter
Indicates that the specified character appears or plays a significant role in the final part or ending segment of a work or event.
-
E.
laterFinale
Indicates that one event, episode, or occurrence serves as a concluding part that happens after another referenced event or finale.
- 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.