Triple
T35018551
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yugur people |
E1010124
|
entity |
| Predicate | traditionalClothingInfluence |
P29110
|
FINISHED |
| Object | Tibetan |
—
|
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: Tibetan | Statement: [Yugur people, traditionalClothingInfluence, Tibetan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalClothingInfluence Context triple: [Yugur people, traditionalClothingInfluence, Tibetan]
-
A.
traditionalClothingType
Indicates the type or category of traditional clothing associated with an entity.
-
B.
traditionalDressVariant
Indicates that one traditional dress is a variant or localized form of another traditional dress within the same broader cultural or stylistic tradition.
-
C.
influencedTradition
chosen
Indicates that one entity has had a shaping or guiding effect on the development, practices, or values of a particular tradition.
-
D.
traditionalDressSimilarTo
Indicates that one traditional dress resembles or shares notable stylistic or cultural features with another traditional dress.
-
E.
clothingSymbolism
Indicates how clothing or attire conveys symbolic meaning, such as status, identity, emotion, or cultural significance, within a given context.
- 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_69f76dcc3ac8819096a3ed52f5fa2523 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff49f888348190b9c55afa73b99e6a |
completed | May 9, 2026, 2:51 p.m. |
| PD | Predicate disambiguation | batch_69ff49614ef88190ac70b034c55ad738 |
completed | May 9, 2026, 2:49 p.m. |
Created at: May 3, 2026, 4:01 p.m.