Triple
T38387028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Menuet (from Suite bergamasque) |
E899605
|
entity |
| Predicate | isDanceInspired |
P104091
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Menuet (from Suite bergamasque), isDanceInspired, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isDanceInspired Context triple: [Menuet (from Suite bergamasque), isDanceInspired, true]
-
A.
hasDanceInfluence
chosen
Indicates that one entity has contributed to shaping, inspiring, or affecting the dance style, technique, or choreography of another entity.
-
B.
hasChoreographyBasedOn
Indicates that one choreography is derived from, inspired by, or structured according to another existing work or source.
-
C.
isSocialDance
Indicates that an activity or event involves dancing primarily for social interaction rather than performance or competition.
-
D.
danceSceneInspired
Indicates that one dance scene is creatively influenced or modeled after another source, such as a different scene, style, or performance.
-
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_69f76e5c9b808190b486523f5c2f817d |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fcd1499e2c81909bafd84dc4810f45 |
completed | May 7, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69fcccf024ec819086383ffbb6cfc036 |
completed | May 7, 2026, 5:33 p.m. |
Created at: May 3, 2026, 4:31 p.m.