Triple
T9051353
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Áo dài |
E216889
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | traditional Vietnamese garment |
C25523
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: traditional Vietnamese garment Context triple: [Áo dài, instanceOf, traditional Vietnamese garment]
-
A.
traditional Indian garment
A traditional Indian garment is a culturally significant piece of clothing, such as a sari, kurta, or dhoti, characterized by its regional styles, vibrant textiles, and often intricate embellishments, worn for daily life, rituals, and celebrations.
-
B.
traditional Malay clothing
Traditional Malay clothing encompasses the culturally significant garments such as baju kurung, baju Melayu, and songket, characterized by modest silhouettes, rich textiles, and intricate decorative motifs that reflect Malay heritage and identity.
-
C.
kimono
A kimono is a traditional Japanese full-length robe with wide sleeves and a wrap-around design, typically secured with an obi sash and worn for both formal and cultural occasions.
-
D.
Dimasa traditional attire element
A Dimasa traditional attire element is a culturally significant garment or accessory, such as woven cloth, jewelry, or headgear, that reflects the identity, customs, and aesthetic heritage of the Dimasa community.
-
E.
baju Melayu style
Baju Melayu style is a traditional Malay men's attire characterized by a loose long-sleeved shirt, matching trousers, and often paired with a sampin (waist cloth) and songkok (cap), typically worn for formal, cultural, and religious occasions.
- F. None of above. chosen
Provenance (1 batch)
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_69ca83d362e88190ae44b4e4dc194209 |
completed | March 30, 2026, 2:08 p.m. |
Created at: March 30, 2026, 7:10 p.m.