Triple
T28331384
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Waltzes |
E717546
|
entity |
| Predicate | primaryKeySignature |
P129885
|
FINISHED |
| Object | various keys |
—
|
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: various keys | Statement: [Waltzes, primaryKeySignature, various keys]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryKeySignature Context triple: [Waltzes, primaryKeySignature, various keys]
-
A.
primaryKeySignatures
chosen
Indicates that the referenced key signatures are the main or authoritative signatures associated with the given entity or context.
-
B.
primaryKeyInstrument
Indicates that the specified instrument is the main or principal instrument associated with an entity or record.
-
C.
primaryIndex
Indicates that one entity serves as the main or default index used to organize, access, or reference another entity within a system or dataset.
-
D.
keyIdentifier
Indicates that one entity serves as a unique key or identifying code used to distinguish or reference another entity.
-
E.
primaryIdentification
Indicates that one identifier is the main or officially recognized identification for an entity among possibly multiple identifiers.
- 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_69eff6e9a57c8190a69c2c74b5d72119 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_6a002ae74da08190a4b47e0ff0f7f8fe |
completed | May 10, 2026, 6:51 a.m. |
| PD | Predicate disambiguation | batch_6a0029cc369c81909578e52c4a75ab18 |
completed | May 10, 2026, 6:46 a.m. |
Created at: April 28, 2026, 12:32 a.m.