Triple
T30498084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jet Song |
E776059
|
entity |
| Predicate | hasChoreographicComponent |
P170264
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Jet Song, hasChoreographicComponent, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChoreographicComponent Context triple: [Jet Song, hasChoreographicComponent, yes]
-
A.
hasChoreographicCharacteristics
Indicates that something possesses specific features, qualities, or attributes related to choreography or choreographic style.
-
B.
choreographyIncludes
chosen
Indicates that a choreography or dance piece contains or incorporates a specific movement, sequence, or component as part of its structure.
-
C.
hasChoreographyBasedOn
Indicates that one choreography is derived from, inspired by, or structured according to another existing work or source.
-
D.
hasDanceChoreography
Indicates that an entity is associated with or characterized by a specific dance choreography.
-
E.
choreographedTo
Indicates that one action, movement, or sequence has been deliberately designed or arranged to align in timing, pattern, or structure with another.
- 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_69f22498c5d481908aaea89e6fab8280 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fd0b92f42881908cd77e3f058adcc2 |
completed | May 7, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fd0a3d68d4819094d92040f7c48d7c |
completed | May 7, 2026, 9:55 p.m. |
Created at: April 29, 2026, 8:14 p.m.