Triple

T435951
Position Surface form Disambiguated ID Type / Status
Subject Kyoto E10010 entity
Predicate formerName P65 FINISHED
Object Heian-kyō 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: Heian-kyō | Statement: [Kyoto, formerName, Heian-kyō]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Heian-kyō
Context triple: [Kyoto, formerName, Heian-kyō]
  • 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. Nara
    Nara is an ancient Japanese city renowned for its early role as a national capital, its historic temples, and its culturally significant deer-filled parks.
  • C. Edo
    Edo was the historical name of Japan’s capital during the Tokugawa shogunate, a major political and cultural center that later became modern Tokyo.
  • D. Sendai
    Sendai is the largest city in Japan’s Tōhoku region, known for its lush greenery, historic sites, and status as a major economic and cultural center in northeastern Honshu.
  • E. Minoh
    Minoh is a suburban city in northern Osaka Prefecture, Japan, known for its scenic Minoh Waterfall, autumn foliage, and residential communities.
  • 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_69a2e8465ef481909655c681b01e2986 completed Feb. 28, 2026, 1:06 p.m.
NER Named-entity recognition batch_69a2ef0b6e0c8190ad6a335ee804829c completed Feb. 28, 2026, 1:35 p.m.
NED1 Entity disambiguation (via context triple) batch_69acce4b94d08190b7747b0b6d61e3e1 completed March 8, 2026, 1:18 a.m.
Created at: Feb. 28, 2026, 1:11 p.m.