Triple
T37413381
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | K. 466 |
E929633
|
entity |
| Predicate | associatedWorkNumbering |
—
|
GENERATED |
| Object | Piano Concerto No. 20 |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
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 (1 batch)
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. |
Created at: May 3, 2026, 4:16 p.m.