Triple
T29028542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | III. Rondo: Allegro non troppo |
E737661
|
entity |
| Predicate | sharesOpusWith |
P195129
|
FINISHED |
| Object | Piano Concerto No. 1 in D minor, Op. 15 |
—
|
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 No. 1 in D minor, Op. 15 | Statement: [III. Rondo: Allegro non troppo, sharesOpusWith, Piano Concerto No. 1 in D minor, Op. 15]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesOpusWith Context triple: [III. Rondo: Allegro non troppo, sharesOpusWith, Piano Concerto No. 1 in D minor, Op. 15]
-
A.
sharesUniverseWith
Indicates that two entities exist within the same fictional or narrative universe, implying shared continuity, setting, or canon.
-
B.
sharesBayWith
Indicates that two locations are situated along or adjacent to the same bay.
-
C.
shareWith
Indicates that something is given, disclosed, or made accessible by one entity to another entity.
-
D.
sharesWith
Indicates that one entity gives another entity access to or use of something it possesses.
-
E.
sharesSystemWith
Indicates that two entities operate within or are associated with the same overarching system or environment.
- 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_69f077ef00fc81909325f084ad37c035 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69fda94697c4819081291967202248be |
completed | May 8, 2026, 9:13 a.m. |
| PD | Predicate disambiguation | batch_69fda5973fcc8190a57daef31fb70a49 |
completed | May 8, 2026, 8:57 a.m. |
| PDg | Predicate description generation | batch_69fda945e1e08190bf923fcd4d2c548a |
completed | May 8, 2026, 9:13 a.m. |
Created at: April 28, 2026, 9:54 a.m.