Triple
T25235859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oo Antava Oo Oo Antava |
E632333
|
entity |
| Predicate | danceStyleInfluence |
P104091
|
FINISHED |
| Object | mass dance performances |
—
|
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: mass dance performances | Statement: [Oo Antava Oo Oo Antava, danceStyleInfluence, mass dance performances]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: danceStyleInfluence Context triple: [Oo Antava Oo Oo Antava, danceStyleInfluence, mass dance performances]
-
A.
hasDanceInfluence
chosen
Indicates that one entity has contributed to shaping, inspiring, or affecting the dance style, technique, or choreography of another entity.
-
B.
movementInfluences
Indicates that one entity’s movement affects, alters, or determines the movement or motion-related behavior of another entity.
-
C.
choreographyStyle
Indicates the specific style or form of choreography associated with a performance, routine, or choreographic work.
-
D.
danceEra
Indicates the historical period or era during which a particular style or form of dance was prominent or originated.
-
E.
danceAbility
Indicates the level or quality of how well an entity can dance.
- 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_69e75a8ec5f88190b9eba06ae42b413a |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f47df954cc8190ab223daad550fd0d |
completed | May 1, 2026, 10:18 a.m. |
| PD | Predicate disambiguation | batch_69f4683472ec8190a483b3b8afe71720 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 1:07 p.m.