Triple
T20133539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kanchipuram silk saree |
E490959
|
entity |
| Predicate | traditionalWearOf |
P46605
|
FINISHED |
| Object | Tamil women |
—
|
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: Tamil women | Statement: [Kanchipuram silk saree, traditionalWearOf, Tamil women]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalWearOf Context triple: [Kanchipuram silk saree, traditionalWearOf, Tamil women]
-
A.
traditionalWearer
chosen
Indicates that an entity customarily wears or is characterized by wearing traditional or culturally specific clothing.
-
B.
typicalWear
Indicates that one entity is commonly or characteristically worn by the other in typical situations or contexts.
-
C.
traditionalDressVariant
Indicates that one traditional dress is a variant or localized form of another traditional dress within the same broader cultural or stylistic tradition.
-
D.
wornStyle
Indicates the manner or fashion in which an item is worn or styled on an entity.
-
E.
traditionalDressSimilarTo
Indicates that one traditional dress resembles or shares notable stylistic or cultural features with another traditional dress.
- 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_69da62651a0c8190a3e05e95e056a66b |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e66763ee908190af64af31b4ca2377 |
completed | April 20, 2026, 5:50 p.m. |
| PD | Predicate disambiguation | batch_69e54cfb0d0081908e789b9b57e96668 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 11:32 p.m.