Triple
T23025467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Honiton pottery |
E573296
|
entity |
| Predicate | handcraftAspect |
P98026
|
FINISHED |
| Object | hand-painted decoration |
—
|
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: hand-painted decoration | Statement: [Honiton pottery, handcraftAspect, hand-painted decoration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: handcraftAspect Context triple: [Honiton pottery, handcraftAspect, hand-painted decoration]
-
A.
traditionalCraft
Indicates that an entity is associated with or practices a craft or skill that is rooted in long-established, culturally transmitted traditions.
-
B.
traditionalCraftCenter
Indicates that a place functions as a hub where traditional crafts are practiced, taught, preserved, or showcased.
-
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.
craftSpecialty
chosen
Indicates that an entity has a particular area of specialized skill or focus within a craft or artisanal practice.
-
E.
isHandmade
Indicates that an object has been crafted or produced by hand rather than by automated or industrial processes.
- 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_69e245b821008190b0e09cb02092aae1 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1847c671c8190a8095051d8c3cf93 |
completed | April 29, 2026, 4:09 a.m. |
| PD | Predicate disambiguation | batch_69ef3ba004a48190885aece88efd1f52 |
completed | April 27, 2026, 10:34 a.m. |
Created at: April 17, 2026, 3:52 p.m.