Triple

T1812832
Position Surface form Disambiguated ID Type / Status
Subject Sapporo E40366 entity
Predicate twinCity P1072 FINISHED
Object Shenyang E20553 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: Shenyang | Statement: [Sapporo, twinCity, Shenyang]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Shenyang
Context triple: [Sapporo, twinCity, Shenyang]
  • A. Shenyang chosen
    Shenyang is a major industrial and historical city in northeastern China and the capital of Liaoning Province.
  • B. Dalian
    Dalian is a major port city in northeastern China known for its strategic location on the Liaodong Peninsula, maritime trade, and modern urban development.
  • C. Changchun
    Changchun is a major city in northeastern China that served as the capital of the Japanese puppet state of Manchukuo during the early 20th century.
  • D. Anshan
    Anshan was an ancient city and region in southwestern Iran that served as an early center of Elamite and later Achaemenid Persian power.
  • E. Jinzhou
    Jinzhou is a prefecture-level port city in southwestern Liaoning Province, northeastern China, known for its industrial base and coastal location on the Bohai Sea.
  • 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_69a88643a3388190a612f2ebe1fb29e7 completed March 4, 2026, 7:21 p.m.
NER Named-entity recognition batch_69aa65c775408190b4f5912786720e28 completed March 6, 2026, 5:27 a.m.
NED1 Entity disambiguation (via context triple) batch_69ae1fc41d248190a149252940dbdb27 completed March 9, 2026, 1:17 a.m.
Created at: March 4, 2026, 7:32 p.m.