Triple
T31227057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | moonwalk (dance) |
E796169
|
entity |
| Predicate | precursorMove |
P57884
|
FINISHED |
| Object | backslide (tap dance) |
—
|
NE NERFINISHED |
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: backslide (tap dance) | Statement: [moonwalk (dance), precursorMove, backslide (tap dance)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: precursorMove Context triple: [moonwalk (dance), precursorMove, backslide (tap dance)]
-
A.
preStatePrecursor
Indicates that one state or condition serves as a precursor to, or exists immediately before, another state in a process or sequence.
-
B.
precededByMovement
Indicates that an event or state occurs only after a prior movement action has taken place.
-
C.
precursorActivity
chosen
Indicates that one activity occurs earlier and contributes causally or preparatorily to the initiation of another activity.
-
D.
successorInMovement
Indicates that one movement directly follows another in a sequence or progression.
-
E.
movedFor
Indicates that one entity changed its location or position for the benefit, purpose, or in response to another entity.
- 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_69f69c52682481909e4bf599202b7414 |
completed | May 3, 2026, 12:52 a.m. |
| PD | Predicate disambiguation | batch_69f696673214819094350e1d2648ef34 |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9:10 p.m.