Triple
T22089226
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carolina Shag |
E545868
|
entity |
| Predicate | danceRhythmPattern |
P7864
|
FINISHED |
| Object | six-count pattern |
—
|
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: six-count pattern | Statement: [Carolina Shag, danceRhythmPattern, six-count pattern]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: danceRhythmPattern Context triple: [Carolina Shag, danceRhythmPattern, six-count pattern]
-
A.
dancePattern
Indicates a recurring or structured way in which an entity performs or organizes a dance or sequence of dance movements.
-
B.
typicalTempoPattern
Indicates the characteristic or commonly occurring tempo progression or rhythmic pattern associated with an action or event.
-
C.
danceStructure
Indicates a structural or organizational relationship between elements within a dance, such as how movements, sections, or patterns are arranged and connected.
-
D.
danceFeature
Indicates that one entity serves as a notable characteristic, element, or attribute of a dance or dancing-related activity.
-
E.
hasRhythmicStyle
chosen
Indicates that one entity exhibits or is characterized by a particular rhythmic pattern or style in its expression or behavior.
- 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_69e11e36d03c8190a83a1ba802b7231b |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f128e47ba08190a208af72a7cc176f |
completed | April 28, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69e71b20ec50819096ac196c798f8e3c |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:29 p.m.