Triple
T37610966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beethoven’s Tenth |
E935782
|
entity |
| Predicate | appliedToComposer |
P152968
|
FINISHED |
| Object | Johannes Brahms |
—
|
NE NERFINISHED |
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: Johannes Brahms | Statement: [Beethoven’s Tenth, appliedToComposer, Johannes Brahms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliedToComposer Context triple: [Beethoven’s Tenth, appliedToComposer, Johannes Brahms]
-
A.
appliesToComponent
Indicates that a rule, condition, or operation is specifically relevant or applicable to a particular component.
-
B.
belongsToComposerPhase
Indicates that a musical work or activity is associated with a particular phase or period in a composer's creative career.
-
C.
performsComposer
Indicates that a performer executes or interprets a musical work composed by a specific composer.
-
D.
setComposer
Indicates that an entity assigns or specifies another entity as the composer of a work or item.
-
E.
associatedWithComposerActivity
chosen
Indicates a relationship where something is linked to, involved in, or results from the activities or work of a composer.
- 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_69f76ed0a85481909254a8a89090c826 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ffb69812808190a751853b30183e65 |
completed | May 9, 2026, 10:35 p.m. |
| PD | Predicate disambiguation | batch_69ffb63bdda88190a9dd8426dc0bad43 |
completed | May 9, 2026, 10:33 p.m. |
Created at: May 3, 2026, 4:18 p.m.