Triple
T21249758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FWV 48 |
E523710
|
entity |
| Predicate | workKeySignature |
P143378
|
FINISHED |
| Object | D 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 minor | Statement: [FWV 48, workKeySignature, D minor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workKeySignature Context triple: [FWV 48, workKeySignature, D minor]
-
A.
signatureWork
Indicates that the work is a defining or most representative creation associated with an entity (such as a person, group, or organization).
-
B.
signatureWorkType
Indicates the specific category or type of work that serves as a defining or primary example associated with an entity.
-
C.
noteSignature
Indicates that one entity serves as a signature or identifying mark attached to a note created or associated with another entity.
-
D.
signatureWorkSeries
Indicates that a work is part of a designated "signature" series or collection associated with a creator, brand, or entity.
-
E.
signaturePractice
Indicates that an entity engages in or is associated with a characteristic or defining practice, method, or style that serves as its signature.
- 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_69e0b5146c108190adc9adb73e90abff |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7359c7a648190b4345336ac3be024 |
completed | April 21, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69e5f61239708190ab7b3c83ae848a0d |
completed | April 20, 2026, 9:46 a.m. |
| PDg | Predicate description generation | batch_69e5f9943ed881909ef49045c5bcf6df |
completed | April 20, 2026, 10:01 a.m. |
Created at: April 16, 2026, 3:56 p.m.