Triple
T35138632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fugue in D-sharp minor, BWV 853 |
E1014640
|
entity |
| Predicate | pairedWorkKey |
P101522
|
FINISHED |
| Object | D-sharp minor |
—
|
LITERAL 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: D-sharp minor | Statement: [Fugue in D-sharp minor, BWV 853, pairedWorkKey, D-sharp minor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pairedWorkKey Context triple: [Fugue in D-sharp minor, BWV 853, pairedWorkKey, D-sharp minor]
-
A.
workPairing
Indicates that two entities are associated or grouped together for the purpose of working or collaborating on a task, project, or role.
-
B.
pairedSingleWith
Indicates that one entity is matched or associated as a single counterpart with another single entity, typically forming an exclusive one-to-one pairing.
-
C.
pairedField
Indicates that one field is logically linked or associated with another field as a corresponding pair.
-
D.
workNumberWithinPair
Indicates that an entity’s work number is defined relative to, and falls within, a specific paired grouping or association.
-
E.
associatedWorkKey
chosen
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.
- 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_69f76dd9c1848190af70d4882a2c1ad7 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78ca7c87c81908f1648733f2ea3db |
completed | May 3, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69f78b9106008190930b3b3675b737d6 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4:02 p.m.