Triple
T22830484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chimbarongo |
E565786
|
entity |
| Predicate | hasArtisanCommunity |
P138998
|
FINISHED |
| Object | wicker artisans |
—
|
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: wicker artisans | Statement: [Chimbarongo, hasArtisanCommunity, wicker artisans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasArtisanCommunity Context triple: [Chimbarongo, hasArtisanCommunity, wicker artisans]
-
A.
hasCraftCommunity
chosen
Indicates that an entity is associated with or supports a community engaged in crafting activities.
-
B.
hasCommunityIn
Indicates that a community is present, active, or established within a specified location, platform, or context.
-
C.
hasCommunityAspect
Indicates that something involves, reflects, or contributes to a shared community dimension, such as collective participation, interaction, or benefit.
-
D.
hasCommunityGroup
Indicates that an entity is associated with, or belongs to, a specific community group.
-
E.
isCommunity
Indicates that an entity functions as or is classified as a community, typically representing a group of individuals connected by shared location, interests, or characteristics.
- 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_69e24585ab1c81909b2b5065d15805d5 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17e2ac8d48190b6dc7edc5ad82bc7 |
completed | April 29, 2026, 3:42 a.m. |
| PD | Predicate disambiguation | batch_69eed2d117088190acbfe130d84f8627 |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:34 p.m.