Triple

T3994157
Position Surface form Disambiguated ID Type / Status
Subject Choe Yong-gon E87060 entity
Predicate placeOfDeath P21 FINISHED
Object Pyongyang E24920 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: Pyongyang | Statement: [Choe Yong-gon, placeOfDeath, Pyongyang]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Pyongyang
Context triple: [Choe Yong-gon, placeOfDeath, Pyongyang]
  • A. Pyongyang chosen
    Pyongyang is the capital and largest city of North Korea, serving as its political, economic, and cultural center.
  • B. Sinuiju, Korea
    Sinuiju, Korea is a North Korean city on the Yalu River bordering China, known as an important industrial and transportation hub.
  • C. Wonsan
    Wonsan is a port city on North Korea’s east coast, known for its strategic military importance and role as a regional transportation and industrial hub.
  • D. Seoul
    Seoul is the capital and largest metropolis of South Korea, known as a major global center for technology, culture, and finance.
  • E. Gwangju
    Gwangju is a major metropolitan city in southwestern South Korea known for its rich cultural heritage and pivotal role in the country’s pro-democracy movement.
  • 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_69aed94118148190975e6aa4e554cde9 completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69aefa1d9d8c8190982d092a73d38564 completed March 9, 2026, 4:49 p.m.
NED1 Entity disambiguation (via context triple) batch_69b5403970e08190bb491048b1bd7b16 completed March 14, 2026, 11:02 a.m.
Created at: March 9, 2026, 3:33 p.m.