Triple
T25140626
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Great Gatsby (stage productions) |
E629790
|
entity |
| Predicate | typicalDanceStyle |
P95479
|
FINISHED |
| Object | Charleston |
—
|
NE NERFINISHED |
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: [The Great Gatsby (stage productions), typicalDanceStyle, Charleston]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalDanceStyle Context triple: [The Great Gatsby (stage productions), typicalDanceStyle, Charleston]
-
A.
choreographyStyle
Indicates the specific style or form of choreography associated with a performance, routine, or choreographic work.
-
B.
typeOfDanceFeatured
chosen
Indicates the specific style or category of dance that is highlighted or showcased in a given context or work.
-
C.
folkDanceRhythm
Indicates a rhythmic pattern or beat specifically associated with a traditional folk dance.
-
D.
hasTraditionalDance
Indicates that an entity is associated with, practices, or possesses a specific traditional dance.
-
E.
isSocialDance
Indicates that an activity or event involves dancing primarily for social interaction rather than performance or competition.
- 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_69e2ff338250819096ff6c8892804389 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f7a225a77c81908f8953ccfeb14336 |
completed | May 3, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69f7a06d4f108190bae3ab9ae431d2c7 |
completed | May 3, 2026, 7:22 p.m. |
Created at: April 18, 2026, 6:29 a.m.