Triple

T11270242
Position Surface form Disambiguated ID Type / Status
Subject Taihō Code E266792 entity
Predicate instanceOf P0 FINISHED
Object Japanese historical document C16967 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 historical document
Context triple: [Taihō Code, instanceOf, Japanese historical document]
  • A. Korean historical document
    A Korean historical document is an original written or printed record produced in or about Korea’s past, preserving information on its political, social, cultural, or intellectual history.
  • B. Japanese historical event
    A Japanese historical event is a significant occurrence in Japan’s past—such as a political shift, conflict, cultural transformation, or natural disaster—that notably influenced the nation’s society, governance, or cultural development.
  • C. Japanese historical tale
    A Japanese historical tale is a narrative work that recounts and embellishes real past events, figures, and battles in Japan’s history, blending factual record with literary storytelling.
  • D. Japanese classic text chosen
    A Japanese classic text is a historically significant written work from Japan’s premodern eras that reflects traditional language, culture, thought, and literary or scholarly practices.
  • E. Meiji-period text
    A Meiji-period text is a written work produced in Japan between 1868 and 1912 that reflects the era’s rapid modernization, Western influence, and evolving social, political, and cultural ideas.
  • F. None of above.

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.