Triple
T34321219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aizu cotton |
E880738
|
entity |
| Predicate | hasCraftCategory |
P114787
|
FINISHED |
| Object | Japanese folk textile |
—
|
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: Japanese folk textile | Statement: [Aizu cotton, hasCraftCategory, Japanese folk textile]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCraftCategory Context triple: [Aizu cotton, hasCraftCategory, Japanese folk textile]
-
A.
hasCraftType
chosen
Indicates that an entity is associated with, or classified by, a particular type or category of craft.
-
B.
hasCraft
Indicates a relationship where an entity possesses, operates, or is associated with a particular vehicle, vessel, or other craft.
-
C.
hasCraftName
Indicates that an entity is associated with a specific craft-related name or designation.
-
D.
hasCategoryOn
Indicates that something is assigned to or associated with a specific category within a given context or scope.
-
E.
hasCraftingSystem
Indicates that an entity includes or supports a mechanism for creating or combining items, materials, or components into new objects or resources.
- 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_69f349b9cd508190a996a616903b3e6d |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fcef654d588190b29ecc76678d1aa0 |
completed | May 7, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69fcecdb97f48190b382b7d13be92dc0 |
completed | May 7, 2026, 7:49 p.m. |
Created at: May 1, 2026, 1:57 a.m.