Triple
T20133541
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kanchipuram silk saree |
E490959
|
entity |
| Predicate | hasBorderMaterial |
P138806
|
FINISHED |
| Object | pure silk |
—
|
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: pure silk | Statement: [Kanchipuram silk saree, hasBorderMaterial, pure silk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBorderMaterial Context triple: [Kanchipuram silk saree, hasBorderMaterial, pure silk]
-
A.
hadBorderType
Indicates that a boundary between two entities existed and specifies the nature or classification of that border (e.g., land, maritime, disputed).
-
B.
hasBorderThrough
Indicates that a border between two regions or entities passes through or along a specified intermediate area, feature, or object.
-
C.
hasBorderCode
Indicates that there is an associated code or identifier specifying the type or status of a border between entities.
-
D.
hasWaterBorderWith
Indicates that two entities share a common boundary that runs along or across a body of water, such as a river, lake, or sea.
-
E.
hasWallsMaterial
Indicates that the material specified is used to construct or cover the walls of the referenced entity.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69e54fc2bc3c819088c33cd263303433 |
completed | April 19, 2026, 9:57 p.m. |
Created at: April 11, 2026, 11:32 p.m.