Triple
T27843814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mishing community |
E703759
|
entity |
| Predicate | weaves |
P113984
|
FINISHED |
| Object | traditional 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: traditional shawls | Statement: [Mishing community, weaves, traditional shawls]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: weaves Context triple: [Mishing community, weaves, traditional shawls]
-
A.
weavingDirection
Indicates the orientation or path along which the weaving process is carried out between interlaced elements.
-
B.
hasWeave
Indicates that one entity possesses, exhibits, or is characterized by a particular weave or woven pattern associated with another entity.
-
C.
weaver
chosen
Indicates that an entity engages in the activity or role of weaving, typically creating fabric or similar materials by interlacing threads or fibers.
-
D.
typicalWeavingTechnique
Indicates that one entity is the characteristic or commonly used weaving method associated with another entity.
-
E.
weavingCenter
Indicates that an entity serves as a central place or hub where weaving activities are carried out or coordinated.
- 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_69ef840d9e3c819093615ebff4ec22be |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f638d838c481909fbe470bb85c30b1 |
completed | May 2, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69f6318ae6f08190b3f85f9201046a15 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 6:05 p.m.