Triple
T10285844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Little Colonel |
E241224
|
entity |
| Predicate | hasDanceSequence |
P35114
|
FINISHED |
| Object | staircase tap dance scene |
—
|
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: staircase tap dance scene | Statement: [The Little Colonel, hasDanceSequence, staircase tap dance scene]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDanceSequence Context triple: [The Little Colonel, hasDanceSequence, staircase tap dance scene]
-
A.
hasDanceSequences
chosen
Indicates that the subject contains or features one or more dance sequences as part of its content or activity.
-
B.
hasDanceMove
Indicates that an entity performs, demonstrates, or is associated with a particular dance move.
-
C.
hasDanceChoreography
Indicates that an entity is associated with or characterized by a specific dance choreography.
-
D.
hasDanceSceneWith
Indicates that two entities participate together in a dance scene within the same context or work.
-
E.
hasDanceAssociation
Indicates that there is a relationship or affiliation between an entity and a dance-related organization, group, or activity.
- 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_69d381aaafc08190af475ef58dc16aba |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d7ccb7ec8190a538cf279e48116e |
completed | April 7, 2026, 10:09 a.m. |
| PD | Predicate disambiguation | batch_69d4d1f117708190928f92ae2611d724 |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:40 a.m.