Triple
T31227949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | "Shake Your Body (Down to the Ground)" |
E796194
|
entity |
| Predicate | hasSingleEdit |
P148148
|
FINISHED |
| Object | shorter radio edit |
—
|
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: shorter radio edit | Statement: ["Shake Your Body (Down to the Ground)", hasSingleEdit, shorter radio edit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSingleEdit Context triple: ["Shake Your Body (Down to the Ground)", hasSingleEdit, shorter radio edit]
-
A.
hasSingle
Indicates that an entity possesses exactly one instance of a specified related entity or attribute.
-
B.
hasShortEdit
Indicates that an entity has undergone a brief or minor modification or revision.
-
C.
hasShorterSingleEdit
chosen
Indicates that one entity can be transformed into the other by a single edit operation that results in a shorter form.
-
D.
singleEditLength
Indicates that one entity can be transformed into the other by performing exactly one edit operation (insertion, deletion, or substitution).
-
E.
hasEditingFeature
Indicates that an entity possesses a capability or function related to modifying or editing content.
- 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_69f224da98f88190ab32f690cce5d303 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fccdd496048190bca801a8a9eecb62 |
completed | May 7, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69fcccee6240819084680887731ff64b |
completed | May 7, 2026, 5:33 p.m. |
Created at: April 29, 2026, 9:10 p.m.