Triple
T35671090
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vikten |
E1030717
|
entity |
| Predicate | hasArtisanWorkshop |
P147882
|
FINISHED |
| Object | glassblowing workshop |
—
|
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: glassblowing workshop | Statement: [Vikten, hasArtisanWorkshop, glassblowing workshop]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasArtisanWorkshop Context triple: [Vikten, hasArtisanWorkshop, glassblowing workshop]
-
A.
hasCraftsman
Indicates that one entity serves as the craftsman, maker, or artisan responsible for creating, building, or crafting another entity.
-
B.
workshopOrStudio
chosen
Indicates that one entity functions as a workshop or studio associated with, used by, or belonging to another entity.
-
C.
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.
-
D.
hasArtFacilities
Indicates that an entity provides or is equipped with facilities or resources dedicated to art-related activities.
-
E.
hasNotableCraft
Indicates that an entity is associated with a particularly significant or distinguished craft, skill, or artisanal practice.
- 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_69f76e0acfc0819082c8495c2210ce73 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fe30bc64308190b603ff1b30c2aeee |
completed | May 8, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fe2f7175b081908dd61e1513620bbe |
completed | May 8, 2026, 6:46 p.m. |
Created at: May 3, 2026, 4:05 p.m.