Triple

T9872204
Position Surface form Disambiguated ID Type / Status
Subject Port of Weihai E239983 entity
Predicate locatedIn P40 FINISHED
Object Weihai E177120 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: Weihai | Statement: [Port of Weihai, locatedIn, Weihai]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Weihai
Context triple: [Port of Weihai, locatedIn, Weihai]
  • A. Weihai chosen
    Weihai is a coastal city in eastern China known for its strategic location on the Yellow Sea, maritime history, and role as a major port and tourist destination.
  • B. Qingdao
    Qingdao is a major coastal city in eastern China known for its port, beaches, German colonial architecture, and Tsingtao Brewery.
  • C. Yantai
    Yantai is a coastal city in Shandong Province, China, known for its port, wine production, and scenic beaches along the Bohai Sea.
  • D. Foochow
    Foochow is an older English romanization of the name of Fuzhou, the capital city of Fujian Province in southeastern China.
  • E. Laizhou
    Laizhou is a county-level coastal city in northeastern Shandong Province, China, known for its salt, gold, and chemical industries.
  • 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_69ca84e8a0788190b9061811d50fd554 completed March 30, 2026, 2:12 p.m.
NER Named-entity recognition batch_69cdb3f5cc948190b03186b867c92229 completed April 2, 2026, 12:10 a.m.
NED1 Entity disambiguation (via context triple) batch_69d1eae2189c81909629e4bd46097051 completed April 5, 2026, 4:53 a.m.
Created at: March 30, 2026, 8:37 p.m.