Triple
T30725786
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hob.I:45 |
E782275
|
entity |
| Predicate | hasKeyOfWork |
P180807
|
FINISHED |
| Object | F-sharp 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-sharp minor | Statement: [Hob.I:45, hasKeyOfWork, F-sharp minor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeyOfWork Context triple: [Hob.I:45, hasKeyOfWork, F-sharp minor]
-
A.
hasKeyWork
Indicates that an entity possesses or is associated with a primary or central work (such as a main publication, artwork, or project) that is especially representative or important.
-
B.
hasKeyAccord
Indicates that one entity possesses or defines the primary key or governing agreement that authorizes or controls another entity.
-
C.
workIsKeySourceFor
Indicates that the referenced work serves as a primary or crucial source of information, evidence, or inspiration for the associated entity.
-
D.
hasKeyFunctionInWork
Indicates that an entity serves as a primary or essential function within a particular work or creation.
-
E.
hasKeyAct
Indicates that one entity possesses or is associated with a primary or central action related to 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_69f224ad9f9c81908e02a79ae0001137 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7516d5b4081908588a6feb541f355 |
completed | May 3, 2026, 1:45 p.m. |
| PD | Predicate disambiguation | batch_69f74d40ebb081909daf60623e38f41d |
completed | May 3, 2026, 1:27 p.m. |
| PDg | Predicate description generation | batch_69f7516c538481908c6e55cf76add098 |
completed | May 3, 2026, 1:45 p.m. |
Created at: April 29, 2026, 8:36 p.m.