Triple

T13377843
Position Surface form Disambiguated ID Type / Status
Subject Jinyang E319235 entity
Predicate modernCityName P3207 FINISHED
Object Taiyuan E80116 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: Taiyuan | Statement: [Jinyang, modernCityName, Taiyuan]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Taiyuan
Context triple: [Jinyang, modernCityName, Taiyuan]
  • A. Taiyuan chosen
    Taiyuan is the capital and largest city of Shanxi Province in northern China, known as an important industrial and transportation hub with a long imperial history.
  • B. Taiyuan
    Taiyuan was a historical Chinese era name used during the reign of the Eastern Jin emperor Sun Liang.
  • C. Xinzhou
    Xinzhou is a prefecture-level city in northern China known for its historical sites and location within Shanxi Province’s coal-rich and culturally significant region.
  • D. Datong
    Datong is a historic industrial city in northern China known for its coal production and nearby cultural landmarks such as the Yungang Grottoes.
  • E. Jinzhong
    Jinzhong is a prefecture-level city in northern China known for its historical sites and cultural heritage within Shanxi Province.
  • 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_69d806b886bc8190b676e7768b8e01c5 completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69dadce56c6c8190adf4e19f6d1bc233 completed April 11, 2026, 11:44 p.m.
NED1 Entity disambiguation (via context triple) batch_69f7a83125d481908fe02cf85651a7bb completed May 3, 2026, 7:55 p.m.
Created at: April 9, 2026, 9:33 p.m.