Triple
T37233567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harpsichord Concerto in D minor, BWV 1052 |
E923206
|
entity |
| Predicate | alsoCataloguedAs |
P84753
|
FINISHED |
| Object | F.40 |
—
|
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.40 | Statement: [Harpsichord Concerto in D minor, BWV 1052, alsoCataloguedAs, F.40]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alsoCataloguedAs Context triple: [Harpsichord Concerto in D minor, BWV 1052, alsoCataloguedAs, F.40]
-
A.
alsoListedAs
Indicates that an entity is recorded or referenced under an additional alternative name, identifier, or listing.
-
B.
cataloguedWith
Indicates that an item has been recorded, classified, or registered using a particular cataloging system, method, or identifier.
-
C.
alsoSoldAs
Indicates that one item is marketed or available under an alternative name, label, or product identity.
-
D.
alternativeCatalogNumber
chosen
Indicates that an entity is associated with an additional or substitute catalog number different from its primary catalog identifier.
-
E.
alternativeCataloguing
Indicates that an entity is catalogued or described using an additional or non-primary cataloguing system or scheme.
- 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_69f76ea7f0008190b31b8e30f3d05a71 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb4134225081909fd60703b8cae397 |
completed | May 6, 2026, 1:25 p.m. |
| PD | Predicate disambiguation | batch_69fb35bf767081908de8345358ca7f44 |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:15 p.m.