Triple
T37236577
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yakoma ethnic group |
E923593
|
entity |
| Predicate | hasDanceTraditions |
P24698
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Yakoma ethnic group, hasDanceTraditions, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDanceTraditions Context triple: [Yakoma ethnic group, hasDanceTraditions, yes]
-
A.
hasTraditionalDance
chosen
Indicates that an entity is associated with, practices, or possesses a specific traditional dance.
-
B.
hasLivePerformanceTradition
Indicates that there exists an established custom or practice of performing the subject live, typically before an audience.
-
C.
hasDanceInfluence
Indicates that one entity has contributed to shaping, inspiring, or affecting the dance style, technique, or choreography of another entity.
-
D.
hasTraditionIn
Indicates that a particular tradition, custom, or longstanding practice is present, observed, or established within a specified place, group, or context.
-
E.
hasMulticulturalTradition
Indicates that an entity possesses customs, practices, or heritage derived from or influenced by multiple cultural backgrounds.
- 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_69f76ea9fee88190a589f661d95a7189 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb4134225081909fd60703b8cae397 |
completed | May 6, 2026, 1:25 p.m. |
| PD | Predicate disambiguation | batch_69fb35bf767081908de8345358ca7f44 |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:15 p.m.