Triple
T36006052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Gregorio Armeno |
E1041273
|
entity |
| Predicate | hasWorkshopType |
P197647
|
FINISHED |
| Object | family-run artisan shops |
—
|
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: family-run artisan shops | Statement: [San Gregorio Armeno, hasWorkshopType, family-run artisan shops]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWorkshopType Context triple: [San Gregorio Armeno, hasWorkshopType, family-run artisan shops]
-
A.
hasWorkshops
Indicates that one entity offers, hosts, or is associated with one or more workshops for another entity.
-
B.
hasWorkshopsAt
Indicates that an entity conducts, hosts, or offers workshops at a specified location or venue.
-
C.
workshopInTitleIndicates
Indicates that the presence of the word "workshop" in a title signifies that the associated event, session, or item is a workshop.
-
D.
hasTrainingType
Indicates that an entity is associated with or characterized by a specific type or category of training.
-
E.
hasTypeOfWorkExhibited
Indicates that a subject (such as an exhibition or venue) features or displays a particular type or category of work.
- 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_69f76e2a02208190aedd1f9025a8b300 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fe9fb9735c8190a360b556c9d00b3f |
completed | May 9, 2026, 2:45 a.m. |
| PD | Predicate disambiguation | batch_69fe9eaa88008190a9b2a469dc685002 |
completed | May 9, 2026, 2:40 a.m. |
| PDg | Predicate description generation | batch_69fe9fb88db08190a8f4af350633330e |
completed | May 9, 2026, 2:45 a.m. |
Created at: May 3, 2026, 4:07 p.m.