Triple
T27609559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mutwa |
E700275
|
entity |
| Predicate | artisanalSpecialization |
P98026
|
FINISHED |
| Object | handmade crafts |
—
|
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: handmade crafts | Statement: [Mutwa, artisanalSpecialization, handmade crafts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: artisanalSpecialization Context triple: [Mutwa, artisanalSpecialization, handmade crafts]
-
A.
craftSpecialty
chosen
Indicates that an entity has a particular area of specialized skill or focus within a craft or artisanal practice.
-
B.
traditionalCraft
Indicates that an entity is associated with or practices a craft or skill that is rooted in long-established, culturally transmitted traditions.
-
C.
productionTypeSpecialization
Indicates a relationship where one production type is a more specific or specialized form of another, broader production type.
-
D.
associatedCraftsmen
Indicates that there is a relationship linking an entity to one or more craftsmen who are connected to it through work, creation, or service.
-
E.
artSpecialty
Indicates that an entity’s primary focus, expertise, or specialization is in a particular art form or artistic domain.
- 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_69ef6a4e2e208190b63b7268f405785c |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f64dbbaefc8190952b8320bf4397d8 |
completed | May 2, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f64cacd2c08190aed8a1761d0da679 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 27, 2026, 2:10 p.m.