Triple
T37534635
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orchestral Suite No. 1 in C major, BWV 1066 |
E933160
|
entity |
| Predicate | usesDanceType |
P66999
|
FINISHED |
| Object | courante |
—
|
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: courante | Statement: [Orchestral Suite No. 1 in C major, BWV 1066, usesDanceType, courante]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesDanceType Context triple: [Orchestral Suite No. 1 in C major, BWV 1066, usesDanceType, courante]
-
A.
usesDanceForms
chosen
Indicates that one entity employs or incorporates specific dance forms in its actions, practices, or expressions.
-
B.
usedInDance
Indicates that something is employed or incorporated as a component or element within a dance performance or practice.
-
C.
danceSuitability
Indicates how appropriate or well-suited something (such as music, a space, or attire) is for dancing.
-
D.
hasDanceMove
Indicates that an entity performs, demonstrates, or is associated with a particular dance move.
-
E.
hasDanceAssociation
Indicates that there is a relationship or affiliation between an entity and a dance-related organization, group, or activity.
- 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_69f76ec999288190ae26ec7b6aea7046 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba5eec0448190a5e6f0c43fdcd0e3 |
completed | May 6, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69fba34edd548190bfa980e6e16e0a88 |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.