Triple
T35692784
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BWV 857 |
E1031342
|
entity |
| Predicate | hasKeyOfFugue |
P192456
|
FINISHED |
| Object | F 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: F minor | Statement: [BWV 857, hasKeyOfFugue, F minor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeyOfFugue Context triple: [BWV 857, hasKeyOfFugue, F minor]
-
A.
hasKeyFigure
Indicates that an entity includes, involves, or is characterized by an important or central person relevant to it.
-
B.
hasKeyFunctor
Indicates that one entity serves as the primary or key functor (main functional operator or mapping) associated with another entity.
-
C.
hasKeyFunction
Indicates that one entity serves as a primary or essential function or role for another entity.
-
D.
hasKeyTheorem
Indicates that one entity contains, relies on, or is characterized by a central or foundational theorem associated with the other entity.
-
E.
hasKeyAccord
Indicates that one entity possesses or defines the primary key or governing agreement that authorizes or controls another entity.
- 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_69f76e0c73ec819080ab60a9e2f5f1f6 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd0b92f42881908cd77e3f058adcc2 |
completed | May 7, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fd0a3d68d4819094d92040f7c48d7c |
completed | May 7, 2026, 9:55 p.m. |
| PDg | Predicate description generation | batch_69fd0b92150881909b1166fe6d09aa19 |
completed | May 7, 2026, 10 p.m. |
Created at: May 3, 2026, 4:05 p.m.