Triple
T37413381
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | K. 466 |
E929633
|
entity |
| Predicate | associatedWorkNumbering |
P70295
|
FINISHED |
| Object | Piano Concerto No. 20 |
E272021
|
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. 20 | Statement: [K. 466, associatedWorkNumbering, Piano Concerto No. 20]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWorkNumbering Context triple: [K. 466, associatedWorkNumbering, Piano Concerto No. 20]
-
A.
associatedKeyWorkNumbering
Indicates that a key work is linked to, or identified by, a specific numbering system or reference number.
-
B.
workNumbering
chosen
Indicates that a specific numbering or cataloging identifier is assigned to a work within a larger collection or system.
-
C.
appearsInWorkNumber
Indicates that an entity is featured or occurs within a specific numbered work in a series or collection.
-
D.
associatedWorkKey
Indicates that there is a connection or linkage between one work and another related work, typically identifying the related work by a key or identifier.
-
E.
workNumberInKey
Indicates that a specific work or item is identified or referenced by a particular number used as a key in some cataloging or indexing system.
- 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_6a40824907d08190be2bc2954253b7dd |
completed | June 28, 2026, 2:09 a.m. |
| PD | Predicate disambiguation | batch_6a037a13a1308190a202df66f4781855 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:16 p.m.