Triple
T29026976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phantasie in A minor for piano and orchestra |
E737618
|
entity |
| Predicate | laterReusedIn |
P91997
|
FINISHED |
| Object | Piano Concerto in A minor, Op. 54 |
—
|
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: Piano Concerto in A minor, Op. 54 | Statement: [Phantasie in A minor for piano and orchestra, laterReusedIn, Piano Concerto in A minor, Op. 54]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterReusedIn Context triple: [Phantasie in A minor for piano and orchestra, laterReusedIn, Piano Concerto in A minor, Op. 54]
-
A.
reusedIn
chosen
Indicates that something previously used in one context or instance is used again in another context or instance.
-
B.
laterRepurposedFor
Indicates that something was originally used for one purpose and subsequently assigned a different, new purpose.
-
C.
laterUsedBy
Indicates that something is subsequently utilized or employed by a specified entity at a later time.
-
D.
subsequentUse
Indicates that one entity is used, applied, or consumed after another entity in time or sequence.
-
E.
partiallyReusedAs
Indicates that one entity is used again as part of another entity, but only to a limited or incomplete extent rather than in its entirety.
- 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_69f077ef00fc81909325f084ad37c035 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69fe163a41a0819098403b470e327d29 |
completed | May 8, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fe1358db5c819092570814a37ef5bd |
completed | May 8, 2026, 4:46 p.m. |
Created at: April 28, 2026, 9:53 a.m.