Triple
T35464624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mapuche crafts |
E1025030
|
entity |
| Predicate | typicalCraftsperson |
P206993
|
FINISHED |
| Object | Mapuche women |
—
|
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: Mapuche women | Statement: [Mapuche crafts, typicalCraftsperson, Mapuche women]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalCraftsperson Context triple: [Mapuche crafts, typicalCraftsperson, Mapuche women]
-
A.
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.
-
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.
employedCraftsmenFrom
Indicates that one entity has hired or utilizes craftsmen originating from another entity.
-
D.
hasCraftsman
Indicates that one entity serves as the craftsman, maker, or artisan responsible for creating, building, or crafting another entity.
-
E.
traditionalCraftCenter
Indicates that a place functions as a hub where traditional crafts are practiced, taught, preserved, or showcased.
- F. None of above. chosen
Provenance (4 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_69f76dfa20d0819089585dc2cf653aea |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0324d08190ac5b610cc0f6a38c |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82179081908325a59b8539b3a8 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:04 p.m.