Triple
T24473805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quimper faience |
E617172
|
entity |
| Predicate | notableWorkshop |
P156240
|
FINISHED |
| Object | Henriot Quimper |
—
|
NE NERFINISHED |
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: Henriot Quimper | Statement: [Quimper faience, notableWorkshop, Henriot Quimper]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableWorkshop Context triple: [Quimper faience, notableWorkshop, Henriot Quimper]
-
A.
workshopInTitleIndicates
Indicates that the presence of the word "workshop" in a title signifies that the associated event, session, or item is a workshop.
-
B.
workshopMark
Indicates that an entity has been designated, labeled, or flagged in the context of a workshop-related process or activity.
-
C.
hasWorkshopsAt
Indicates that an entity conducts, hosts, or offers workshops at a specified location or venue.
-
D.
notableStudentWork
Indicates that the subject has a student whose work is particularly notable or significant in relation to the subject.
-
E.
hasWorkshops
Indicates that one entity offers, hosts, or is associated with one or more workshops for another entity.
- 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_69e2d7f197588190889a03e620558059 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f299457ce081909e8d95fd482928dc |
completed | April 29, 2026, 11:50 p.m. |
| PD | Predicate disambiguation | batch_69f287d76c7c81909494f12e606a9149 |
completed | April 29, 2026, 10:36 p.m. |
| PDg | Predicate description generation | batch_69f28f4d978c81908310c01def2514cc |
completed | April 29, 2026, 11:07 p.m. |
Created at: April 18, 2026, 2:20 a.m.