Triple
T20143229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sukarara village |
E491226
|
entity |
| Predicate | hasCraftCenter |
P130895
|
FINISHED |
| Object | weaving cooperatives |
—
|
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: weaving cooperatives | Statement: [Sukarara village, hasCraftCenter, weaving cooperatives]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCraftCenter Context triple: [Sukarara village, hasCraftCenter, weaving cooperatives]
-
A.
hasCraft
Indicates a relationship where an entity possesses, operates, or is associated with a particular vehicle, vessel, or other craft.
-
B.
hasArtCenter
Indicates that an entity possesses, hosts, or includes an art center as one of its facilities or components.
-
C.
traditionalCraftCenter
chosen
Indicates that a place functions as a hub where traditional crafts are practiced, taught, preserved, or showcased.
-
D.
hasNotableCraft
Indicates that an entity is associated with a particularly significant or distinguished craft, skill, or artisanal practice.
-
E.
hasCraftsman
Indicates that one entity serves as the craftsman, maker, or artisan responsible for creating, building, or crafting another entity.
- 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_69da6265f8f0819080b29c752a574088 |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e6679cbc388190bb2b444a69a597a6 |
completed | April 20, 2026, 5:51 p.m. |
| PD | Predicate disambiguation | batch_69e54cfb0d0081908e789b9b57e96668 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 11:33 p.m.