Triple
T17194387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | осетины |
E417308
|
entity |
| Predicate | традиционныйТанец |
P24698
|
FINISHED |
| Object | осетинские народные танцы |
—
|
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: осетинские народные танцы | Statement: [осетины, традиционныйТанец, осетинские народные танцы]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: традиционныйТанец Context triple: [осетины, традиционныйТанец, осетинские народные танцы]
-
A.
hasTraditionalDance
chosen
Indicates that an entity is associated with, practices, or possesses a specific traditional dance.
-
B.
nationalDance
Indicates that a particular dance is officially recognized as the national dance of a country or nation.
-
C.
folkDanceRhythm
Indicates a rhythmic pattern or beat specifically associated with a traditional folk dance.
-
D.
danceForm
Indicates that one entity is a style or type of dance associated with the other entity.
-
E.
danceShow
Indicates that one entity presents or performs a dance-related show or performance for another or for an audience.
- 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_69d886d6ba8c819093215917b3d01689 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42da93bf88190b60b658087779d36 |
completed | April 19, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69e383141ae0819096acd71683637cbc |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:38 a.m.