Triple
T32742143
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Resurrection |
E837243
|
entity |
| Predicate | associatedWithWorkRankInComposerOutput |
P205148
|
FINISHED |
| Object | second symphony |
—
|
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: second symphony | Statement: [Resurrection, associatedWithWorkRankInComposerOutput, second symphony]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithWorkRankInComposerOutput Context triple: [Resurrection, associatedWithWorkRankInComposerOutput, second symphony]
-
A.
associatedWithComposerName
Indicates that an entity has an association or connection with a composer identified by the given name.
-
B.
isRelatedWorkOfComposer
Indicates that one work is associated with or connected to a particular composer, typically as a composition created by that composer.
-
C.
associatedWithComposerRole
Indicates that an entity is connected to another entity specifically in the capacity or role of a composer.
-
D.
associatedWorkComposer
Indicates that a person or entity is the composer responsible for creating the associated work.
-
E.
followedByInComposerWork
Indicates that one element in a composer's work directly succeeds another in sequence within that same composition.
- F. None of above. chosen
Provenance (4 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_69f34936e1748190b797e406e4e9293a |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a0379f0cbe481909b4b8fc6cbe297f0 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037cab06288190b093935f235ddff2 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 1:12 a.m.