Triple

T6825001
Position Surface form Disambiguated ID Type / Status
Subject Kyocera E156991 entity
Predicate foundedIn P41 FINISHED
Object Kyoto, Japan E10010 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: Kyoto, Japan | Statement: [Kyocera, foundedIn, Kyoto, Japan]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kyoto, Japan
Context triple: [Kyocera, foundedIn, Kyoto, Japan]
  • A. Kyoto chosen
    Kyoto is a historic Japanese city renowned for its well-preserved temples, traditional wooden houses, and role as the former imperial capital.
  • B. Yamashina, Kyoto
    Yamashina, Kyoto is a ward in eastern Kyoto, Japan, known historically as an early temple site and as a residential area linking central Kyoto with the neighboring Shiga Prefecture.
  • C. Kita-ku, Kyoto
    Kita-ku, Kyoto is a northern ward of Kyoto, Japan, known for its historic temples, traditional neighborhoods, and scenic mountainous surroundings.
  • D. Fushimi-ku, Kyoto
    Fushimi-ku, Kyoto is a ward in southern Kyoto City known for its historic sake breweries, traditional streetscapes, and major Shinto shrines.
  • E. Kamigyo-ku, Kyoto
    Kamigyo-ku, Kyoto is a central ward of Kyoto City known for its historic neighborhoods, traditional culture, and many important temples and shrines.
  • 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_69c6882a5b5c8190917a7db9ed36bad1 completed March 27, 2026, 1:37 p.m.
NER Named-entity recognition batch_69c6d581ea5881908ba78c6bf1ce58ee completed March 27, 2026, 7:07 p.m.
NED1 Entity disambiguation (via context triple) batch_69c7ad6644f4819080db0a3981470d96 completed March 28, 2026, 10:28 a.m.
Created at: March 27, 2026, 2:18 p.m.