Triple

T6373618
Position Surface form Disambiguated ID Type / Status
Subject Taizhou E143408 entity
Predicate borderedBy P224 FINISHED
Object Yancheng E141797 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: Yancheng | Statement: [Taizhou, borderedBy, Yancheng]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Yancheng
Context triple: [Taizhou, borderedBy, Yancheng]
  • A. Yancheng chosen
    Yancheng is a coastal prefecture-level city in eastern China known for its wetlands, nature reserves, and rapidly developing economy.
  • B. Nantong
    Nantong is a coastal city in eastern China known for its textile industry, river and sea ports, and location on the northern bank of the Yangtze River opposite Shanghai.
  • C. Changzhou
    Changzhou is a major industrial and commercial city in Jiangsu Province, eastern China, known for its manufacturing base and location along the Yangtze River.
  • D. Suqian
    Suqian is a prefecture-level city in northern Jiangsu Province, China, known for its historical sites and growing industrial and agricultural economy.
  • E. Zhenjiang
    Zhenjiang is a historic port city in eastern China known for its strategic location on the Yangtze River and its rich cultural and culinary heritage.
  • 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_69c008d9f4348190ab598a2913259a1c completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c068390af08190967a3d25ec9a50e5 completed March 22, 2026, 10:07 p.m.
NED1 Entity disambiguation (via context triple) batch_69c64badc3c481908199bf32069cc1c7 completed March 27, 2026, 9:19 a.m.
Created at: March 22, 2026, 4:33 p.m.