Triple

T15496512
Position Surface form Disambiguated ID Type / Status
Subject Tokoname E378830 entity
Predicate hasSisterCity P919 FINISHED
Object Yixing E566273 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: Yixing | Statement: [Tokoname, hasSisterCity, Yixing]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Yixing
Context triple: [Tokoname, hasSisterCity, Yixing]
  • A. Yixing chosen
    Yixing is a county-level city in southern Jiangsu Province, China, renowned for its traditional purple clay teapots and ceramics.
  • B. Wuxi
    Wuxi is a major industrial and cultural city in eastern China, located near Lake Tai and known for its manufacturing, canals, and historic gardens.
  • C. Tongxiang
    Tongxiang is a county-level city in northern Zhejiang Province, China, known for administering the historic water town of Wuzhen.
  • D. Liyang
    Liyang is a county-level city in Jiangsu Province, China, known for its scenic attractions such as Tianmu Lake and its administration under the prefecture-level city of Changzhou.
  • E. Xiantao
    Xiantao is a county-level city in central China’s Hubei province, known for its location on the Jianghan Plain and its role as a regional agricultural and industrial center.
  • 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_69d85cd53a7c819080f5b9042c4c199e completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69e03faecd60819091eeaa56c9c8f67d completed April 16, 2026, 1:47 a.m.
NED1 Entity disambiguation (via context triple) batch_69ff5f2d4b1c81909ff876289db20803 completed May 9, 2026, 4:22 p.m.
Created at: April 10, 2026, 3:52 a.m.