Triple
T20133530
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kanchipuram silk saree |
E490959
|
entity |
| Predicate | isWovenBy |
P113984
|
FINISHED |
| Object | traditional weavers |
—
|
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: traditional weavers | Statement: [Kanchipuram silk saree, isWovenBy, traditional weavers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isWovenBy Context triple: [Kanchipuram silk saree, isWovenBy, traditional weavers]
-
A.
hasWeave
Indicates that one entity possesses, exhibits, or is characterized by a particular weave or woven pattern associated with another entity.
-
B.
weaver
chosen
Indicates that an entity engages in the activity or role of weaving, typically creating fabric or similar materials by interlacing threads or fibers.
-
C.
typicalWeavingTechnique
Indicates that one entity is the characteristic or commonly used weaving method associated with another entity.
-
D.
weavingCenter
Indicates that an entity serves as a central place or hub where weaving activities are carried out or coordinated.
-
E.
خيوط التطريز
Indicates the relationship of being threads specifically used for embroidery work.
- 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.