Triple
T23609774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Tap Dance Kid |
E583004
|
entity |
| Predicate | notableChoreographyStyle |
P12046
|
FINISHED |
| Object | tap dance |
—
|
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: tap dance | Statement: [The Tap Dance Kid, notableChoreographyStyle, tap dance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableChoreographyStyle Context triple: [The Tap Dance Kid, notableChoreographyStyle, tap dance]
-
A.
choreographyStyle
chosen
Indicates the specific style or form of choreography associated with a performance, routine, or choreographic work.
-
B.
notableDance
Indicates that the subject is especially recognized or distinguished for a particular dance or dancing performance.
-
C.
notableDanceSection
Indicates that a specific segment or portion of a performance is recognized as a particularly significant or distinguished dance section.
-
D.
hasChoreographyBasedOn
Indicates that one choreography is derived from, inspired by, or structured according to another existing work or source.
-
E.
typeOfDanceFeatured
Indicates the specific style or category of dance that is highlighted or showcased in a given context or work.
- 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_69e248faa2788190abb1581742daa6aa |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b0f399cc8190a18d94b60fdca042 |
completed | April 29, 2026, 7:19 a.m. |
| PD | Predicate disambiguation | batch_69f118d0e0588190a86527a7747c5427 |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:44 p.m.