Triple

T755981
Position Surface form Disambiguated ID Type / Status
Subject Lincoln, Lincolnshire, England E15556 entity
Predicate hasTwinTown P919 FINISHED
Object Tangshan E123029 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: Tangshan | Statement: [Lincoln, Lincolnshire, England, hasTwinTown, Tangshan]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tangshan
Context triple: [Lincoln, Lincolnshire, England, hasTwinTown, Tangshan]
  • A. Tangshan chosen
    Tangshan is a major industrial city in northern China, historically known for its coal mining, steel production, and the devastating 1976 earthquake.
  • B. 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.
  • C. Anyang
    Anyang is an ancient city in northern China renowned as one of the historical capitals of the Shang dynasty and a major archaeological site.
  • D. Shijiazhuang
    Shijiazhuang is the capital and largest city of Hebei Province in northern China, known as a major industrial and transportation hub.
  • E. Ma’anshan
    Ma’anshan is an industrial city in eastern China known for its steel production and location along the lower Yangtze River.
  • 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_69a493599a0081908da65f3407af1ef2 completed March 1, 2026, 7:28 p.m.
NER Named-entity recognition batch_69a4a6693cbc8190a167e12a896d7ce7 completed March 1, 2026, 8:49 p.m.
NED1 Entity disambiguation (via context triple) batch_69ac4bf512bc81908ff403ce87337a0d completed March 7, 2026, 4:01 p.m.
Created at: March 1, 2026, 7:37 p.m.