Triple

T23292514
Position Surface form Disambiguated ID Type / Status
Subject Chūmon (Middle Gate) E590069 entity
Predicate hasRomanization P2508 FINISHED
Object Chūmon 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: Chūmon | Statement: [Chūmon (Middle Gate), hasRomanization, Chūmon]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Chūmon
Context triple: [Chūmon (Middle Gate), hasRomanization, Chūmon]
  • A. Chūmon chosen
    Chūmon is the central gate of Hōryū-ji, one of Japan’s oldest and most significant Buddhist temple complexes.
  • B. Chōgen
    Chōgen was a Japanese era name (nengō) used during the reign of Emperor Go-Ichijō in the early 11th century.
  • C. Hozomon
    Hozomon is the grand inner gate of Senso-ji Temple in Asakusa, Tokyo, known for its massive red lanterns and imposing traditional architecture.
  • D. Chōkai
    Chōkai was a Takao-class heavy cruiser of the Imperial Japanese Navy that served prominently in World War II, including major Pacific naval battles.
  • E. Chōryaku
    Chōryaku was a Japanese era name (nengō) used during the Heian period, marking a specific span of years in the imperial calendar.
  • 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_69e25d1af9d88190a0b9b5e8fa608618 completed April 17, 2026, 4:17 p.m.
NER Named-entity recognition batch_69f196cc20c08190a6a678befe1061dd completed April 29, 2026, 5:27 a.m.
Created at: April 17, 2026, 5:02 p.m.