Triple
T18505351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Get Your Number (music video) |
E452183
|
entity |
| Predicate | danceElement |
P103855
|
FINISHED |
| Object | synchronized routines with female dancers |
—
|
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: synchronized routines with female dancers | Statement: [Get Your Number (music video), danceElement, synchronized routines with female dancers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: danceElement Context triple: [Get Your Number (music video), danceElement, synchronized routines with female dancers]
-
A.
danceAbility
Indicates the level or quality of how well an entity can dance.
-
B.
danceFeature
chosen
Indicates that one entity serves as a notable characteristic, element, or attribute of a dance or dancing-related activity.
-
C.
danceForm
Indicates that one entity is a style or type of dance associated with the other entity.
-
D.
danceProp
Indicates that one entity is used or involved as a prop in another entity’s dance performance or dancing activity.
-
E.
danceStructure
Indicates a structural or organizational relationship between elements within a dance, such as how movements, sections, or patterns are arranged and connected.
- 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_69d8d386df84819092355ebb260d848e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e53341b6c48190b7da42f5df923e81 |
completed | April 19, 2026, 7:55 p.m. |
| PD | Predicate disambiguation | batch_69e469dbf5208190b6fc49e02a087f54 |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:36 a.m.