Triple

T22024766
Position Surface form Disambiguated ID Type / Status
Subject Yumedono E543931 entity
Predicate name P16 FINISHED
Object Yumedono NE NERFINISHED

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: Yumedono | Statement: [Yumedono, name, Yumedono]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Yumedono
Context triple: [Yumedono, name, Yumedono]
  • A. Yumedono chosen
    Yumedono is a renowned octagonal hall within the Hōryū-ji temple complex in Nara, Japan, celebrated for its elegant Asuka-period architecture and important Buddhist statues.
  • B. Yamadera
    Yamadera is a historic mountainside temple complex in Japan’s Tohoku region, famed for its scenic cliffside halls and panoramic valley views.
  • C. Yumenoshima
    Yumenoshima is a reclaimed island in Tokyo Bay known for its parks, sports and recreational facilities, and former landfill history.
  • D. Yamatokoriyama
    Yamatokoriyama is a Japanese city in Nara Prefecture known for its historic Koriyama Castle and traditional goldfish breeding industry.
  • E. Takamikura
    Takamikura is the ornate imperial throne used in Kyoto for the enthronement ceremonies of Japanese emperors.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e11e2e8ea4819084210fe06d3a1b8d completed April 16, 2026, 5:36 p.m.
NER Named-entity recognition batch_69f127ca45a08190b2d5d3a8eb37cb4b completed April 28, 2026, 9:34 p.m.
Created at: April 16, 2026, 8:23 p.m.