Triple
T22656244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Menuet II |
E559232
|
entity |
| Predicate | cataloguedUnder |
P107050
|
FINISHED |
| Object | HWV 351 (as part of the suite) |
—
|
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: HWV 351 (as part of the suite) | Statement: [Menuet II, cataloguedUnder, HWV 351 (as part of the suite)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cataloguedUnder Context triple: [Menuet II, cataloguedUnder, HWV 351 (as part of the suite)]
-
A.
catalogued as
chosen
Indicates that one entity has been recorded or registered under a specific identifier or entry within a catalog or systematic listing.
-
B.
catalogedBy
Indicates that an item or resource has been organized, described, or recorded in a catalog by a particular agent or system.
-
C.
subjectOfCatalog
Indicates that something is the primary focus or entry described within a catalog or cataloging record.
-
D.
isClassifiedUnder
Indicates that one entity is categorized or grouped within a broader class, type, or category represented by another entity.
-
E.
discoveredInCatalogue
Indicates that an entity was identified or first recognized through information found in a specific catalogue.
- 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_69e245489dd88190b1f674acf61c8769 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1765b93dc8190a0357dd4b6ae524a |
completed | April 29, 2026, 3:09 a.m. |
| PD | Predicate disambiguation | batch_69ee6294c4c08190b7e4829f4b9af24b |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:06 p.m.