Triple
T38335763
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chilkat people |
E1037951
|
entity |
| Predicate | hasWeavingDesignFeature |
P64189
|
FINISHED |
| Object | curvilinear formline designs |
—
|
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: curvilinear formline designs | Statement: [Chilkat people, hasWeavingDesignFeature, curvilinear formline designs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWeavingDesignFeature Context triple: [Chilkat people, hasWeavingDesignFeature, curvilinear formline designs]
-
A.
hasWeave
Indicates that one entity possesses, exhibits, or is characterized by a particular weave or woven pattern associated with another entity.
-
B.
textileFeature
chosen
Indicates a characteristic, property, or notable aspect associated with a textile or fabric.
-
C.
typicalWeavingTechnique
Indicates that one entity is the characteristic or commonly used weaving method associated with another entity.
-
D.
hasFlowerMotif
Indicates that one entity features or is decorated with a flower-themed design or pattern in relation to another entity.
-
E.
weavingDirection
Indicates the orientation or path along which the weaving process is carried out between interlaced elements.
- 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_69f76e20d65c81909619ac0dd85c56f0 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fcef654d588190b29ecc76678d1aa0 |
completed | May 7, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69fcecdb97f48190b382b7d13be92dc0 |
completed | May 7, 2026, 7:49 p.m. |
Created at: May 3, 2026, 4:30 p.m.