Triple

T13528071
Position Surface form Disambiguated ID Type / Status
Subject Arita and Imari ceramics region E323061 entity
Predicate hasTraditionalTechnique P3047 FINISHED
Object kiln firing 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: kiln firing | Statement: [Arita and Imari ceramics region, hasTraditionalTechnique, kiln firing]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasTraditionalTechnique
Context triple: [Arita and Imari ceramics region, hasTraditionalTechnique, kiln firing]
  • A. hasTechnique chosen
    Indicates that an entity employs, utilizes, or is associated with a particular method, procedure, or technique.
  • B. hasTraditionalFormIn
    Indicates that something possesses a customary or historically established form or representation within a specified context, system, or location.
  • C. isTraditional
    Indicates that something adheres to long-established customs, practices, or norms rather than modern or innovative ones.
  • D. hasTraditionalSymbol
    Indicates that something is associated with or represented by a conventional or culturally established symbol.
  • E. hasTraditionalBase
    Indicates that something is supported by, built upon, or derived from an established traditional foundation or practice.
  • 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_69d80766a21881909f21a1b7421d3b8a completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69dbafb8e0cc8190b47f6aeb8ced470e completed April 12, 2026, 2:44 p.m.
PD Predicate disambiguation batch_69dbae1046c48190b4ee98c6c9cb9d85 completed April 12, 2026, 2:37 p.m.
Created at: April 9, 2026, 9:44 p.m.