Triple
T12993948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shipoopi |
E321983
|
entity |
| Predicate | hasChoreographyType |
P12046
|
FINISHED |
| Object | ensemble dance number |
—
|
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: ensemble dance number | Statement: [Shipoopi, hasChoreographyType, ensemble dance number]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChoreographyType Context triple: [Shipoopi, hasChoreographyType, ensemble dance number]
-
A.
hasDanceChoreography
Indicates that an entity is associated with or characterized by a specific dance choreography.
-
B.
choreographyStyle
chosen
Indicates the specific style or form of choreography associated with a performance, routine, or choreographic work.
-
C.
choreographedTo
Indicates that one action, movement, or sequence has been deliberately designed or arranged to align in timing, pattern, or structure with another.
-
D.
hasDanceMovement
Indicates that one entity includes, performs, or is characterized by a specific dance movement associated with another entity.
-
E.
hasDanceMove
Indicates that an entity performs, demonstrates, or is associated with a particular dance move.
- 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_69d8076479b8819090afce3591939cdf |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97f2a71a0819098bb6cf8a4b2208a |
completed | April 10, 2026, 10:52 p.m. |
| PD | Predicate disambiguation | batch_69d97dbdd94c8190ac4bbecca02dc77b |
completed | April 10, 2026, 10:46 p.m. |
Created at: April 9, 2026, 8:44 p.m.