Triple
T35138630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fugue in D-sharp minor, BWV 853 |
E1014640
|
entity |
| Predicate | workNumberWithinBook |
P83262
|
FINISHED |
| Object | 8 |
—
|
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: 8 | Statement: [Fugue in D-sharp minor, BWV 853, workNumberWithinBook, 8]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workNumberWithinBook Context triple: [Fugue in D-sharp minor, BWV 853, workNumberWithinBook, 8]
-
A.
appearsInBookNumber
Indicates that an entity is featured or mentioned in a specific book identified by its number within a series or collection.
-
B.
numberInAnthology
chosen
Indicates the specific position or sequence number that a work occupies within an anthology.
-
C.
seriesNumberOfWorks
Indicates that an entity is assigned a specific position or sequence number within a series of related works.
-
D.
authorWorkNumber
Indicates the specific ordinal number or position of a work within an author's body of works.
-
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.
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_69f76dd9c1848190af70d4882a2c1ad7 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78ca7c87c81908f1648733f2ea3db |
completed | May 3, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69f78b9106008190930b3b3675b737d6 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4:02 p.m.