Triple
T3812971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tsuboya Pottery Museum |
E93178
|
entity |
| Predicate | relatedCraft |
P5963
|
FINISHED |
| Object | Ryukyu pottery |
—
|
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: Ryukyu pottery | Statement: [Tsuboya Pottery Museum, relatedCraft, Ryukyu pottery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedCraft Context triple: [Tsuboya Pottery Museum, relatedCraft, Ryukyu pottery]
-
A.
traditionalCraft
chosen
Indicates that an entity is associated with or practices a craft or skill that is rooted in long-established, culturally transmitted traditions.
-
B.
craftGuild
Indicates that an entity is a member of, affiliated with, or governed by a particular craft guild organization.
-
C.
hasCraftsman
Indicates that one entity serves as the craftsman, maker, or artisan responsible for creating, building, or crafting another entity.
-
D.
associatedWithArtForm
Indicates a relationship where an entity is connected or linked to a particular art form, such as by practice, creation, representation, or influence.
-
E.
inspiredWorks
Indicates that one work served as a source of inspiration or creative influence for the creation or development of another work.
- 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_69aed96a60088190ab1df8390fffc935 |
completed | March 9, 2026, 2:30 p.m. |
| NER | Named-entity recognition | batch_69aef1515c688190a38332aedeed8a76 |
completed | March 9, 2026, 4:12 p.m. |
| PD | Predicate disambiguation | batch_69aee7482d708190a3ec74745b102a4c |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:16 p.m.