Triple
T32706244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tokoname ware |
E836278
|
entity |
| Predicate | hasKilnType |
P174808
|
FINISHED |
| Object | climbing kilns (noborigama) |
—
|
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: climbing kilns (noborigama) | Statement: [Tokoname ware, hasKilnType, climbing kilns (noborigama)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKilnType Context triple: [Tokoname ware, hasKilnType, climbing kilns (noborigama)]
-
A.
hasCeramicsType
Indicates that an entity is associated with or classified by a specific type or category of ceramics.
-
B.
hasPotteryType
Indicates that an entity is associated with or characterized by a specific type or category of pottery.
-
C.
hasTypeOfPottery
Indicates that an entity is associated with or characterized by a specific type or category of pottery.
-
D.
associatedWithKilnArea
Indicates a relationship where something is functionally or spatially connected to, or part of, a kiln area.
-
E.
hasQuarryType
Indicates that an entity functions as or is associated with a quarry of a specified type.
- 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_69f3493446148190819541f3ffe79975 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6c851d2488190a93924bca6b167d1 |
completed | May 3, 2026, 4 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f617c08190a70ba880210f908c |
completed | May 3, 2026, 3:41 a.m. |
| PDg | Predicate description generation | batch_69f6c77500a08190b2bdeca33bd2ac08 |
completed | May 3, 2026, 3:56 a.m. |
Created at: May 1, 2026, 1:10 a.m.