Triple
T28416897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mazurkas (Chopin) |
E719830
|
entity |
| Predicate | keyVariety |
P164475
|
FINISHED |
| Object | various major and minor 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 major and minor keys | Statement: [Mazurkas (Chopin), keyVariety, various major and minor keys]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyVariety Context triple: [Mazurkas (Chopin), keyVariety, various major and minor keys]
-
A.
keyType
Indicates the classification or category of a key in relation to how it is used or defined within a system or context.
-
B.
keys
Indicates that one entity serves as a key (or set of keys) that can open, access, or control another entity.
-
C.
key
Indicates that one entity functions as a key (literal or metaphorical) that unlocks, enables access to, or provides a crucial solution or control over another entity.
-
D.
keyCustom
Indicates that something has a user-defined or non-standard key used for identification, access, or configuration.
-
E.
keyExample
Indicates that something serves as a representative or illustrative instance of a key concept, feature, or case.
- 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_69eff6f1c5088190bc24bfbf92f9c017 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f64dc18ab081908ea8baa9edec31e2 |
completed | May 2, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f641e2f1708190b45b48d6a43c51d2 |
completed | May 2, 2026, 6:26 p.m. |
| PDg | Predicate description generation | batch_69f64bca8574819095e081cbb7e2f369 |
completed | May 2, 2026, 7:08 p.m. |
Created at: April 28, 2026, 1:31 a.m.