Triple
T11590144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BWV 232 |
E274858
|
entity |
| Predicate | partiallyBasedOn |
P7125
|
FINISHED |
| Object | earlier cantata movements by Bach |
—
|
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: earlier cantata movements by Bach | Statement: [BWV 232, partiallyBasedOn, earlier cantata movements by Bach]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partiallyBasedOn Context triple: [BWV 232, partiallyBasedOn, earlier cantata movements by Bach]
-
A.
partiallySupportedBy
Indicates that something receives incomplete, limited, or not fully sufficient support from another entity.
-
B.
isBasedOn
chosen
Indicates that one entity is derived from, inspired by, or developed using the content, structure, or principles of another entity.
-
C.
partlyDefinedBy
Indicates that one entity’s nature, role, or characteristics are only partially determined or specified by another entity.
-
D.
isPartially
Indicates that one entity is included within another to some extent, but not completely or fully.
-
E.
basedOnBy
Indicates that one entity is derived from, justified by, or constructed using another entity as its source, foundation, or reference.
- 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_69d6aae6b14c81908dc5a74bad7591f9 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d894643ae48190837502b713f5b9c6 |
completed | April 10, 2026, 6:10 a.m. |
| PD | Predicate disambiguation | batch_69d85dcbacd0819094d4a1237055affa |
completed | April 10, 2026, 2:17 a.m. |
Created at: April 8, 2026, 9:38 p.m.