Triple
T11282205
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lolita fashion |
E267091
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Japanese fashion subculture |
C29487
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Japanese fashion subculture Context triple: [Lolita fashion, instanceOf, Japanese fashion subculture]
-
A.
Japanese custom
A Japanese custom is a traditional practice, behavior, or ritual rooted in Japan’s cultural, social, or religious heritage that guides everyday conduct and communal life.
-
B.
Japanese rite of passage
A Japanese rite of passage is a culturally significant ceremony or practice that marks a major transition in an individual’s life, such as birth, coming of age, marriage, or entering old age, often blending Shinto, Buddhist, and secular traditions.
-
C.
Japanese architectural movement
A Japanese architectural movement is a conceptual category encompassing distinct periods or schools of architectural thought and practice in Japan, characterized by shared design principles, aesthetics, technologies, and cultural or historical contexts.
-
D.
Japanese idol
A Japanese idol is a young entertainer, often a singer, dancer, or model, who is carefully produced and promoted to embody an idealized image of charm, innocence, and approachability for devoted fans.
-
E.
Javanese clothing
Javanese clothing encompasses the traditional garments, such as batik, kebaya, and beskap, characterized by intricate patterns, symbolic motifs, and refined aesthetics that reflect Javanese cultural values and social status.
- F. None of above. chosen
Provenance (1 batch)
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_69d6aac8c2f48190ad0596f1f89f0470 |
completed | April 8, 2026, 7:21 p.m. |
Created at: April 8, 2026, 9:31 p.m.