Triple
T11331242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carnaval de Guaranda |
E268347
|
entity |
| Predicate | danceStyles |
P20189
|
FINISHED |
| Object | traditional Andean dances |
—
|
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: traditional Andean dances | Statement: [Carnaval de Guaranda, danceStyles, traditional Andean dances]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: danceStyles Context triple: [Carnaval de Guaranda, danceStyles, traditional Andean dances]
-
A.
choreographyStyle
Indicates the specific style or form of choreography associated with a performance, routine, or choreographic work.
-
B.
danceForm
chosen
Indicates that one entity is a style or type of dance associated with the other entity.
-
C.
danceProp
Indicates that one entity is used or involved as a prop in another entity’s dance performance or dancing activity.
-
D.
typeOfDanceFeatured
Indicates the specific style or category of dance that is highlighted or showcased in a given context or work.
-
E.
danceStructure
Indicates a structural or organizational relationship between elements within a dance, such as how movements, sections, or patterns are arranged and connected.
- 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_69d6aacb1f0881908c84a349fd1be047 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9fd38308190a5458be1bfcc89ea |
completed | April 9, 2026, 6:03 p.m. |
| PD | Predicate disambiguation | batch_69d787afe5a48190b8af1a3e19529641 |
completed | April 9, 2026, 11:04 a.m. |
Created at: April 8, 2026, 9:32 p.m.