Triple
T33575608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A minor |
E860021
|
entity |
| Predicate | sharesKeySignatureWith |
P200847
|
FINISHED |
| Object | C major |
—
|
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: C major | Statement: [A minor, sharesKeySignatureWith, C major]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesKeySignatureWith Context triple: [A minor, sharesKeySignatureWith, C major]
-
A.
sharesSignsWith
Indicates that two entities exhibit the same or overlapping signs, symptoms, or observable indicators.
-
B.
workKeySignature
Indicates the key signature associated with a musical work, specifying the tonal center and accidentals that characterize that work.
-
C.
sharesNameWith
Indicates that two entities have the same name or an identical naming designation.
-
D.
sharesRecordWith
Indicates that two entities have at least one record or data entry in common, or are both associated with the same record.
-
E.
primaryKeySignatures
Indicates that the referenced key signatures are the main or authoritative signatures associated with the given entity or context.
- 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_69f3497d37848190afcbb5ef3f5c7376 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ffb1f0b03c81909ddb81f07ce74e88 |
completed | May 9, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_69ffb1662b2481908582e0612744f4c5 |
completed | May 9, 2026, 10:12 p.m. |
| PDg | Predicate description generation | batch_69ffb1f001948190a63c493b596a97b9 |
completed | May 9, 2026, 10:15 p.m. |
Created at: May 1, 2026, 1:40 a.m.