Triple

T1910557
Position Surface form Disambiguated ID Type / Status
Subject Hotto Motto Field Kobe E38099 entity
Predicate sponsor P67 FINISHED
Object Hotto Motto E212065 NE 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: Hotto Motto | Statement: [Hotto Motto Field Kobe, sponsor, Hotto Motto]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hotto Motto
Context triple: [Hotto Motto Field Kobe, sponsor, Hotto Motto]
  • A. Hotto Motto chosen
    Hotto Motto is a Japanese take-out bento chain known for offering a wide variety of freshly prepared boxed meals at affordable prices.
  • B. Honancho
    Honancho is a neighborhood in Tokyo, Japan, known as a residential area with convenient access to central city districts via the Tokyo Metro Marunouchi Line.
  • C. Umihotaru
    Umihotaru is a man-made island in Tokyo Bay that serves as a rest area and service complex along the Tokyo Bay Aqua-Line expressway.
  • D. Hieda no Are
    Hieda no Are was a Japanese court reciter traditionally credited with memorizing the oral histories that formed the basis of the early 8th-century chronicle Kojiki.
  • E. Otsunegoten
    Otsunegoten is a historically significant residence within the Kyoto Imperial Palace complex, associated with the Japanese imperial family.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69a8862a26088190aae5243695aeefc0 completed March 4, 2026, 7:21 p.m.
NER Named-entity recognition batch_69abb1b88db48190a9229a7416054a85 completed March 7, 2026, 5:03 a.m.
NED1 Entity disambiguation (via context triple) batch_69adf3d5972881908856b75b324a1ad2 completed March 8, 2026, 10:10 p.m.
Created at: March 4, 2026, 7:35 p.m.