Triple
T13925932
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mizos |
E334860
|
entity |
| Predicate | haveTextileTradition |
P74917
|
FINISHED |
| Object | handwoven shawls |
—
|
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: handwoven shawls | Statement: [Mizos, haveTextileTradition, handwoven shawls]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: haveTextileTradition Context triple: [Mizos, haveTextileTradition, handwoven shawls]
-
A.
textileFeature
Indicates a characteristic, property, or notable aspect associated with a textile or fabric.
-
B.
textileType
chosen
Indicates the specific kind or category of textile material associated with an entity.
-
C.
sharesDesignTraditionWith
Indicates that two entities originate from or participate in the same design tradition, sharing common stylistic principles, methods, or heritage.
-
D.
traditionalCountryIncludes
Indicates that a traditional or culturally defined country encompasses or contains a given subregion or area.
-
E.
traditionalDressVariant
Indicates that one traditional dress is a variant or localized form of another traditional dress within the same broader cultural or stylistic tradition.
- 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_69d81c5f739081908bc05b2461f54828 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2aa7e9248190b0523415b9224e2f |
completed | April 14, 2026, 11:53 a.m. |
| PD | Predicate disambiguation | batch_69de059e4ba881908554f72e889719fa |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:16 p.m.