Triple
T35566061
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BWV 856 |
E1027775
|
entity |
| Predicate | workNumberInBookI |
P183265
|
FINISHED |
| Object | 6 |
—
|
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: 6 | Statement: [BWV 856, workNumberInBookI, 6]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workNumberInBookI Context triple: [BWV 856, workNumberInBookI, 6]
-
A.
workNumberInOpus8
Indicates that a work is assigned a specific number within Opus 8 of a composer’s catalog.
-
B.
worksNumber
Indicates that an entity is identified or referenced by a specific works number, typically denoting a particular work, item, or production instance.
-
C.
workNumberInKey
Indicates that a specific work or item is identified or referenced by a particular number used as a key in some cataloging or indexing system.
-
D.
appearsInWorkNumber
Indicates that an entity is featured or occurs within a specific numbered work in a series or collection.
-
E.
workNumbering
Indicates that a specific numbering or cataloging identifier is assigned to a work within a larger collection or system.
- 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_69f76e020fd8819081cb080e7e203083 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79a54aa3c8190b2bb5d790b2d42d4 |
completed | May 3, 2026, 6:56 p.m. |
| PD | Predicate disambiguation | batch_69f7961970408190b669cc556e30a608 |
completed | May 3, 2026, 6:38 p.m. |
| PDg | Predicate description generation | batch_69f79a53ccc481908421ae16e69aa8a4 |
completed | May 3, 2026, 6:56 p.m. |
Created at: May 3, 2026, 4:04 p.m.