Triple
T11713347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Revue Nègre |
E278426
|
entity |
| Predicate | featuredDanceStyle |
P95479
|
FINISHED |
| Object | Charleston |
—
|
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: Charleston | Statement: [Revue Nègre, featuredDanceStyle, Charleston]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuredDanceStyle Context triple: [Revue Nègre, featuredDanceStyle, Charleston]
-
A.
typeOfDanceFeatured
chosen
Indicates the specific style or category of dance that is highlighted or showcased in a given context or work.
-
B.
choreographyStyle
Indicates the specific style or form of choreography associated with a performance, routine, or choreographic work.
-
C.
featuresProfessionalDancer
Indicates that an entity includes or presents a professional dancer as part of its content, composition, or offering.
-
D.
musicAndDance
Indicates a relationship where music is performed, accompanied by, or integrated with dance as a coordinated activity or event.
-
E.
featuresDanceNumber
Indicates that the subject includes or presents a dance performance or choreographed dance sequence.
- 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_69d6aaff2ce88190b4a1e4b341ad5377 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a4be10088190854699385d1f6a95 |
completed | April 10, 2026, 7:20 a.m. |
| PD | Predicate disambiguation | batch_69d88a7d483081909c2a101087515d74 |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:40 p.m.