Triple
T35232804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BWV 850 |
E1017286
|
entity |
| Predicate | precededByInWTCI |
P163874
|
FINISHED |
| Object | Prelude and Fugue in C-sharp minor, BWV 849 |
—
|
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 C-sharp minor, BWV 849 | Statement: [BWV 850, precededByInWTCI, Prelude and Fugue in C-sharp minor, BWV 849]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: precededByInWTCI Context triple: [BWV 850, precededByInWTCI, Prelude and Fugue in C-sharp minor, BWV 849]
-
A.
wasPrecededBy
Indicates that one event, state, or entity occurred or existed earlier in time than another.
-
B.
precededByInBand
Indicates that one element occurs earlier than another within the ordered sequence of items in the same band or grouping.
-
C.
usedToPrecede
Indicates that one entity regularly or habitually came before another in time or sequence in the past.
-
D.
precededByInPosition
chosen
Indicates that one entity occurs or appears immediately before another entity in a specific ordered position or sequence.
-
E.
precededByUse
Indicates that one use, action, or event occurs earlier in time and is directly followed by another specified use, action, or event.
- 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_69f76de12e4c8190bc46b71a32858356 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd783fed9c81909e792702636c4f1f |
completed | May 8, 2026, 5:44 a.m. |
| PD | Predicate disambiguation | batch_69fd7788e63c81909de22fdafcfe41c0 |
completed | May 8, 2026, 5:41 a.m. |
Created at: May 3, 2026, 4:02 p.m.