Triple
T27151740
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rosalie (1937 film) |
E682406
|
entity |
| Predicate | hasDanceFocus |
P88673
|
FINISHED |
| Object | tap dancing |
—
|
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: tap dancing | Statement: [Rosalie (1937 film), hasDanceFocus, tap dancing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDanceFocus Context triple: [Rosalie (1937 film), hasDanceFocus, tap dancing]
-
A.
hasDanceMovement
Indicates that one entity includes, performs, or is characterized by a specific dance movement associated with another entity.
-
B.
hasDanceMove
chosen
Indicates that an entity performs, demonstrates, or is associated with a particular dance move.
-
C.
hasDanceQuality
Indicates that something possesses a particular characteristic or attribute related to dance, such as style, skill, or expressive quality.
-
D.
hasDanceAssociation
Indicates that there is a relationship or affiliation between an entity and a dance-related organization, group, or activity.
-
E.
hasDancePosition
Indicates that one entity occupies or is assigned a specific position or role within a dance formation or choreography.
- 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_69eefaceb2a08190b9659b7f730629f5 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c663be481908f233d25d28713a4 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 9:14 a.m.