Triple
T37413417
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | K. 466 |
E929633
|
entity |
| Predicate | relatedWorkByGenre |
P122929
|
FINISHED |
| Object | Piano Concerto No. 21 in C major, K. 467 |
E274865
|
NE 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: Piano Concerto No. 21 in C major, K. 467 | Statement: [K. 466, relatedWorkByGenre, Piano Concerto No. 21 in C major, K. 467]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedWorkByGenre Context triple: [K. 466, relatedWorkByGenre, Piano Concerto No. 21 in C major, K. 467]
-
A.
hasGenreOfWorkItAppearsIn
Indicates that an entity is associated with the genre of the work in which it appears.
-
B.
belongsToWorkGenre
Indicates that a creative work is classified under or associated with a particular genre.
-
C.
relatedWorkByArtist
Indicates that one work is connected to another through having been created by the same artist.
-
D.
relatedWorkBySubject
Indicates a relationship where one work is connected to another through sharing the same subject or topic.
-
E.
genreRelation
chosen
Indicates a relationship where one entity is categorized as having, belonging to, or being associated with a particular genre defined by another entity.
- F. None of above.
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_69f76ebde49481908566cd96b37ccc84 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a409521acd481908337b47186f59a29 |
completed | June 28, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_6a037a13a1308190a202df66f4781855 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:16 p.m.