Triple

T4299589
Position Surface form Disambiguated ID Type / Status
Subject Guangxi Zhuang Autonomous Region E99799 entity
Predicate containsCity P294 FINISHED
Object Beihai E56871 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: Beihai | Statement: [Guangxi Zhuang Autonomous Region, containsCity, Beihai]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Beihai
Context triple: [Guangxi Zhuang Autonomous Region, containsCity, Beihai]
  • A. Beihai chosen
    Beihai is a coastal city in China's Guangxi Zhuang Autonomous Region, known for its beaches, maritime trade, and the scenic Silver Beach tourist area.
  • B. Beibu Wan
    Beibu Wan is the Chinese name for the Gulf of Tonkin, a large body of water in the South China Sea bordered by China and Vietnam.
  • C. Wanning
    Wanning is a county-level coastal city in southeastern Hainan, China, known for its tropical climate, beaches, and surf-friendly bays.
  • D. Nanhai
    Nanhai is an alternative name for Nanhai Lake, a notable body of water often associated with scenic and cultural significance in its region.
  • E. Chuansha
    Chuansha is a subdistrict in Shanghai’s Pudong New Area known for its blend of traditional town features and rapidly developing urban infrastructure.
  • 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_69b345528ebc8190b5abc7e95094792d completed March 12, 2026, 10:59 p.m.
NER Named-entity recognition batch_69b3509e8cb481909ccca7992aac31a3 completed March 12, 2026, 11:47 p.m.
NED1 Entity disambiguation (via context triple) batch_69b5c74a1a7c8190a69a82a8a2a38db9 completed March 14, 2026, 8:38 p.m.
Created at: March 12, 2026, 11:08 p.m.