Triple
T2696886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | El Jaleo |
E58531
|
entity |
| Predicate | mainFigureGesture |
P16866
|
FINISHED |
| Object | dynamic dance pose |
—
|
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: dynamic dance pose | Statement: [El Jaleo, mainFigureGesture, dynamic dance pose]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainFigureGesture Context triple: [El Jaleo, mainFigureGesture, dynamic dance pose]
-
A.
signatureGesture
Indicates a distinctive or characteristic gesture that is uniquely associated with a particular individual or entity.
-
B.
hasCentralFigure
Indicates that something features a primary or most important figure at its core or focus.
-
C.
publicFigure
Indicates that an entity is widely recognized by the public and holds a prominent or influential role in society, such as in politics, entertainment, or media.
-
D.
movementRepresentedBy
Indicates that a movement or motion of an entity is depicted, encoded, or symbolized by another entity (such as a sign, pattern, or representation).
-
E.
gesture
chosen
Indicates that an entity uses a bodily movement or sign to communicate or express something 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_69ab4ac269e481909cb317d79e68b75b |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abda3112108190a5e49c13368cf83f |
completed | March 7, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69abd81ea5d88190ab5c8f8b8064b931 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:55 p.m.