Triple
T26407023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chanderi silk |
E663860
|
entity |
| Predicate | warpMaterial |
P160511
|
FINISHED |
| Object | 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: silk | Statement: [Chanderi silk, warpMaterial, silk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: warpMaterial Context triple: [Chanderi silk, warpMaterial, silk]
-
A.
warpProgram
Indicates that an entity modifies or transforms a program’s structure or behavior, typically to optimize, adapt, or otherwise alter how it executes.
-
B.
hasWarp
Indicates that one entity possesses, is equipped with, or is capable of using a warp or warp-related mechanism in relation to another entity or context.
-
C.
shadeMaterial
Indicates that one entity serves as the material or substance used to provide shade for another entity.
-
D.
materialEffect
Indicates that one material causes, influences, or brings about a change in the properties, behavior, or state of another material or system.
-
E.
imageMaterial
Indicates that one entity serves as the material or physical medium from which the image entity is composed or rendered.
- 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_69ee883931888190901be96d75ee23cc |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f610f980788190babd4aca7dd78065 |
completed | May 2, 2026, 2:58 p.m. |
| PD | Predicate disambiguation | batch_69f5f800fa9c8190aab0962669fde8ac |
completed | May 2, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69f6018ceb1c8190a6a5f84071659a96 |
completed | May 2, 2026, 1:52 p.m. |
Created at: April 26, 2026, 11:35 p.m.