Triple
T19791071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coptic textiles |
E475409
|
entity |
| Predicate | producedByTechnique |
P35199
|
FINISHED |
| Object | tapestry weave |
—
|
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: tapestry weave | Statement: [Coptic textiles, producedByTechnique, tapestry weave]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: producedByTechnique Context triple: [Coptic textiles, producedByTechnique, tapestry weave]
-
A.
usedByTechnique
Indicates that a particular technique makes use of or employs the referenced entity as part of its method or process.
-
B.
artisticTechnique
Indicates the method, style, or process used to create or execute an artistic work.
-
C.
hasProductionMethod
chosen
Indicates that one entity is produced, created, or manufactured using the method, process, or technique specified by another entity.
-
D.
hasTechnique
Indicates that an entity employs, utilizes, or is associated with a particular method, procedure, or technique.
-
E.
producedAs
Indicates that one entity is created, generated, or brought into existence as a result or output of another entity or process.
- 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_69d8e51b014081908b263e167370529a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e653c217bc819092c517b27ca22087 |
completed | April 20, 2026, 4:26 p.m. |
| PD | Predicate disambiguation | batch_69e53053ed2881908400becdfada7fd3 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:49 p.m.