Triple
T35157807
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BWV 849 |
E1015174
|
entity |
| Predicate | hasCollectionOrder |
—
|
GENERATED |
| Object | C-sharp minor pair in chromatic sequence of WTC I |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCollectionOrder Context triple: [BWV 849, hasCollectionOrder, C-sharp minor pair in chromatic sequence of WTC I]
-
A.
hasElementOrder
Indicates that one entity is ordered or ranked relative to another within a sequence or hierarchy.
-
B.
hasColumnOrder
Indicates that one column in a sequence is positioned before or after another column, specifying their relative ordering.
-
C.
areOrderedBy
Indicates that a set of items is arranged or sequenced according to a specified criterion or ordering rule.
-
D.
hasCanonicalOrdering
Indicates that there is a standard, agreed-upon sequence in which the related elements should be arranged or considered.
-
E.
hasOrderStructure
chosen
Indicates that there is a defined ordering relation imposed on the elements of a set or collection, specifying how they are arranged or compared in terms of order.
- F. None of above.
Provenance (1 batch)
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_69f76ddb3a708190b521ba2970b17178 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:02 p.m.