Triple
T25685447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ali-Aye-Ligang |
E644054
|
entity |
| Predicate | danceStyleFeature |
P103855
|
FINISHED |
| Object | rhythmic steps symbolizing cultivation |
—
|
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: rhythmic steps symbolizing cultivation | Statement: [Ali-Aye-Ligang, danceStyleFeature, rhythmic steps symbolizing cultivation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: danceStyleFeature Context triple: [Ali-Aye-Ligang, danceStyleFeature, rhythmic steps symbolizing cultivation]
-
A.
danceFeature
chosen
Indicates that one entity serves as a notable characteristic, element, or attribute of a dance or dancing-related activity.
-
B.
choreographyStyle
Indicates the specific style or form of choreography associated with a performance, routine, or choreographic work.
-
C.
danceAbility
Indicates the level or quality of how well an entity can dance.
-
D.
danceProp
Indicates that one entity is used or involved as a prop in another entity’s dance performance or dancing activity.
-
E.
typeOfDanceFeatured
Indicates the specific style or category of dance that is highlighted or showcased in a given context or work.
- 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_69e77e8046888190b07ffa58c7e2c37a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f600c18a14819081b5914dd3b0f9cf |
completed | May 2, 2026, 1:48 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fba5248190945acf1561280799 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 21, 2026, 8:07 p.m.