Triple
T15637976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sindhi topi |
E375993
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Sindhi cultural artifact |
C36447
|
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: Sindhi cultural artifact Context triple: [Sindhi topi, instanceOf, Sindhi cultural artifact]
-
A.
Sundanese cultural artifact
A Sundanese cultural artifact is a tangible object—such as traditional instruments, textiles, tools, or ritual items—that embodies the artistic expression, social values, and historical heritage of the Sundanese people of West Java, Indonesia.
-
B.
Indus Valley Civilization artifact
An Indus Valley Civilization artifact is a material object—such as pottery, seals, tools, ornaments, or architectural remains—created or used by the people of the Indus Valley Civilization, reflecting their technology, trade, social organization, and cultural practices.
-
C.
Zulu cultural artifact
A Zulu cultural artifact is a tangible object—such as beadwork, weaponry, pottery, or ceremonial attire—that embodies the artistic expression, social values, and historical traditions of the Zulu people.
-
D.
Punjabi folk dance
Punjabi folk dance is a vibrant, high-energy traditional dance form from the Punjab region, characterized by rhythmic footwork, expressive gestures, and colorful attire performed to lively folk music.
-
E.
variety of Sindhi
A variety of Sindhi is a distinct form or dialect of the Sindhi language characterized by unique phonological, lexical, and grammatical features associated with a particular region, community, or social group.
- 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_69d85cd035a48190b73d5579ab73969a |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 4:14 a.m.