Triple
T16831843
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Pedro La Laguna |
E409168
|
entity |
| Predicate | hasArtisanProduct |
P3585
|
FINISHED |
| Object | handwoven textiles |
—
|
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 textiles | Statement: [San Pedro La Laguna, hasArtisanProduct, handwoven textiles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasArtisanProduct Context triple: [San Pedro La Laguna, hasArtisanProduct, handwoven textiles]
-
A.
hasCraft
Indicates a relationship where an entity possesses, operates, or is associated with a particular vehicle, vessel, or other craft.
-
B.
hasProduct
chosen
Indicates that an entity possesses, offers, or is associated with a particular product.
-
C.
hasCraftsman
Indicates that one entity serves as the craftsman, maker, or artisan responsible for creating, building, or crafting another entity.
-
D.
hasCulturalProduct
Indicates that an entity possesses, produces, or is associated with a cultural artifact, work, or output (such as art, literature, music, or media).
-
E.
hasArtisanActivity
Indicates that an entity engages in or is associated with a specific craft or artisan-related activity.
- 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_69d883952b048190887740a980b712ed |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b317af8c8190a09cb6d60d28e342 |
completed | April 18, 2026, 4:36 p.m. |
| PD | Predicate disambiguation | batch_69e32b87b4248190aaddb05e88452356 |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:23 a.m.