Triple
T9391287
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Motown 25: Yesterday, Today, Forever performance of Billie Jean in 1983 |
E226030
|
entity |
| Predicate | featuresDanceMove |
P59821
|
FINISHED |
| Object | moonwalk |
—
|
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: moonwalk | Statement: [Motown 25: Yesterday, Today, Forever performance of Billie Jean in 1983, featuresDanceMove, moonwalk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresDanceMove Context triple: [Motown 25: Yesterday, Today, Forever performance of Billie Jean in 1983, featuresDanceMove, moonwalk]
-
A.
featuresDanceNumber
Indicates that the subject includes or presents a dance performance or choreographed dance sequence.
-
B.
danceProp
Indicates that one entity is used or involved as a prop in another entity’s dance performance or dancing activity.
-
C.
featuresDanceTeam
Indicates that something includes or presents a dance team as part of its composition, offering, or program.
-
D.
danceForm
Indicates that one entity is a style or type of dance associated with the other entity.
-
E.
movementName
chosen
Indicates the specific title or designation assigned to a particular movement or action.
- 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_69ca842f7e3481908bf5bcf52e032dbd |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd510d7a9c8190a74ccdb5478dedc9 |
completed | April 1, 2026, 5:08 p.m. |
| PD | Predicate disambiguation | batch_69cca545b2448190a4297312e39c21ac |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:45 p.m.