Triple

T18288168
Position Surface form Disambiguated ID Type / Status
Subject Jiaojiang River system E438036 entity
Predicate hasMouthNear P350 FINISHED
Object Taizhou 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: Taizhou | Statement: [Jiaojiang River system, hasMouthNear, Taizhou]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Taizhou
Context triple: [Jiaojiang River system, hasMouthNear, Taizhou]
  • A. Taizhou
    Taizhou is a prefecture-level city in eastern China known for its historical heritage and location along the Yangtze River in Jiangsu province.
  • B. Taizhou chosen
    Taizhou is a coastal prefecture-level city in eastern China known for its manufacturing industry, port facilities, and location along the East China Sea.
  • C. Wenzhou
    Wenzhou is a major coastal city in southeastern Zhejiang Province, China, known for its entrepreneurial culture, export-driven economy, and large overseas Chinese community.
  • D. Zhoushan City
    Zhoushan City is a prefecture-level port city in Zhejiang Province, China, comprising a large archipelago and serving as a major maritime and fishing hub in the East China Sea.
  • E. Lúzhōu
    Lúzhōu is the standard Hanyu Pinyin romanization of the Chinese city name Luzhou.
  • 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_69d8b914530c8190b4474d862a2b2a1b completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e500fc49b88190bd5b562e0a959e9d completed April 19, 2026, 4:21 p.m.
Created at: April 10, 2026, 10:35 a.m.