Triple

T15779442
Position Surface form Disambiguated ID Type / Status
Subject Toyota City E382573 entity
Predicate hasFormerName P65 FINISHED
Object Koromo 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: Koromo | Statement: [Toyota City, hasFormerName, Koromo]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Koromo
Context triple: [Toyota City, hasFormerName, Koromo]
  • A. Koromo chosen
    Koromo was the former name of what is now Toyota City in Aichi Prefecture, Japan, historically known as a regional center before becoming synonymous with the Toyota automobile company.
  • B. Tokoro
    Tokoro is a coastal district of Kitami City in Hokkaido, Japan, known historically for its fishing industry and drift ice along the Sea of Okhotsk.
  • C. Shinshiro
    Shinshiro is a city in eastern Aichi Prefecture, Japan, known for its mountainous scenery, historic battle sites, and traditional rural landscapes.
  • D. Yakusho
    Yakusho is the family name of acclaimed Japanese actor Kōji Yakusho, known for his prominent roles in both Japanese and international cinema.
  • E. Shimotsuki
    Shimotsuki was a Japanese destroyer of the Imperial Japanese Navy that served in World War II before being sunk in late 1944.
  • 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_69d86da09a10819082fe9797b23e4664 completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e053fea90081908e3fe4f91475bead completed April 16, 2026, 3:14 a.m.
Created at: April 10, 2026, 4:48 a.m.