Triple
T26062561
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nishijin district |
E657301
|
entity |
| Predicate | hasProductUse |
P8225
|
FINISHED |
| Object | formal kimono |
—
|
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: formal kimono | Statement: [Nishijin district, hasProductUse, formal kimono]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProductUse Context triple: [Nishijin district, hasProductUse, formal kimono]
-
A.
hasHumanUse
chosen
Indicates that something is used, employed, or utilized by humans for a particular purpose or benefit.
-
B.
usesProduct
Indicates that one entity makes use of, applies, or employs a particular product.
-
C.
hasByproductUse
Indicates that something produces a secondary material, substance, or outcome that is subsequently used or utilized for another purpose.
-
D.
hasProductionUse
Indicates that something is utilized or applied within a production or operational environment.
-
E.
usedForProduct
Indicates that one entity serves as a tool, component, or means specifically employed in the creation, operation, or delivery of another entity considered as a product.
- 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_69ee5bbd788481909e22bd7153d0c037 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f7b2f3a104819098ddd8909eaf596c |
completed | May 3, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f7b1b8a9fc8190a1279e67a2d12707 |
completed | May 3, 2026, 8:36 p.m. |
Created at: April 26, 2026, 7:19 p.m.