Triple
T36054121
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BWV 865 |
E1042897
|
entity |
| Predicate | followedByInWTCBookI |
P198742
|
FINISHED |
| Object | Prelude and Fugue in B-flat major, BWV 866 |
—
|
NE NERFINISHED |
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: Prelude and Fugue in B-flat major, BWV 866 | Statement: [BWV 865, followedByInWTCBookI, Prelude and Fugue in B-flat major, BWV 866]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followedByInWTCBookI Context triple: [BWV 865, followedByInWTCBookI, Prelude and Fugue in B-flat major, BWV 866]
-
A.
followedByInWTCI
chosen
Indicates that one event, state, or item occurs immediately after another within the context of the WTCI sequence or framework.
-
B.
precededByInWTCBookI
Indicates that one item appears earlier than another in the ordered sequence of content in WTC Book I.
-
C.
followedByInHonor
Indicates that one entity is succeeded by another as a deliberate act of tribute, remembrance, or respect toward the first entity.
-
D.
followedByTitle
Indicates that one title directly succeeds another in a sequence or ordered list.
-
E.
followedByTournament
Indicates that one event or period is immediately succeeded by a tournament.
- 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_69f76e2e41f8819091f9fb0536920fec |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff246e0d4481908bcec718e1d4025b |
completed | May 9, 2026, 12:11 p.m. |
| PD | Predicate disambiguation | batch_69ff23cb70ac81909b776ace4597ae9c |
completed | May 9, 2026, 12:08 p.m. |
Created at: May 3, 2026, 4:08 p.m.