Triple
T37764506
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bourrée from Partita No. 3 in E major, BWV 1006 |
E941376
|
entity |
| Predicate | approximateCompositionDecade |
P7068
|
FINISHED |
| Object | 1720s |
—
|
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: 1720s | Statement: [Bourrée from Partita No. 3 in E major, BWV 1006, approximateCompositionDecade, 1720s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateCompositionDecade Context triple: [Bourrée from Partita No. 3 in E major, BWV 1006, approximateCompositionDecade, 1720s]
-
A.
isAssociatedWithDecade
Indicates that something has a notable connection or relevance to a particular decade.
-
B.
builtInDecade
Indicates that a structure or object was constructed during a specific decade.
-
C.
decadeRecognition
Indicates that an entity is formally recognized, honored, or notable during a specific decade.
-
D.
decade
chosen
Indicates that the relationship or event is associated with, occurs within, or is characteristic of a specific ten-year time period.
-
E.
demarcatedInDecade
Indicates that the temporal boundaries or defining characteristics of something are set or established within a specific decade.
- 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_69f76ee3251881909bb4451aad50752b |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ffcf46fd688190907fd1ceb499a8d1 |
completed | May 10, 2026, 12:20 a.m. |
| PD | Predicate disambiguation | batch_69ffccde2a8c81908e055e74077dbd19 |
completed | May 10, 2026, 12:10 a.m. |
Created at: May 3, 2026, 4:19 p.m.