Triple
T26296916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Huapango huasteco |
E661441
|
entity |
| Predicate | danceSurface |
P78088
|
FINISHED |
| Object | tarima |
—
|
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: tarima | Statement: [Huapango huasteco, danceSurface, tarima]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: danceSurface Context triple: [Huapango huasteco, danceSurface, tarima]
-
A.
danceBackground
Indicates that one entity serves as the background or setting for another entity’s dancing activity.
-
B.
danceFeature
Indicates that one entity serves as a notable characteristic, element, or attribute of a dance or dancing-related activity.
-
C.
hasDanceFloor
chosen
Indicates that a place or venue includes a designated area intended for dancing.
-
D.
danceProp
Indicates that one entity is used or involved as a prop in another entity’s dance performance or dancing activity.
-
E.
danceAction
Indicates an action where an entity performs or engages in dancing, typically involving rhythmic or expressive body movements.
- 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_69ee812cd48c81908054068f545f0526 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f612607c388190ab61d1ac7d18e08d |
completed | May 2, 2026, 3:04 p.m. |
| PD | Predicate disambiguation | batch_69f611a9272881909093360472be832c |
completed | May 2, 2026, 3 p.m. |
Created at: April 26, 2026, 10:13 p.m.