Triple

T17091568
Position Surface form Disambiguated ID Type / Status
Subject Kim Chaek Iron and Steel Complex E414738 entity
Predicate locatedIn P40 FINISHED
Object Chongjin E1249725 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: Chongjin | Statement: [Kim Chaek Iron and Steel Complex, locatedIn, Chongjin]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Chongjin
Context triple: [Kim Chaek Iron and Steel Complex, locatedIn, Chongjin]
  • A. Chongjin chosen
    Chongjin is a major industrial port city in northeastern North Korea and the administrative and economic center of North Hamgyong Province.
  • B. Chongju
    Chongju is a city in northwestern North Korea known as an administrative and transportation center in North Pyongan Province.
  • 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. Dandong
    Dandong is a northeastern Chinese border city on the Yalu River, known as a key gateway for trade and transport between China and North Korea.
  • E. Kim Chaek City
    Kim Chaek City is an industrial port city in North Hamgyong Province, North Korea, named in honor of the Korean War general and politician Kim Chaek.
  • 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_69d886cfc8e88190b05ba466edd35591 completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e3dbfa09b08190be4303dd0d174feb completed April 18, 2026, 7:31 p.m.
NED1 Entity disambiguation (via context triple) batch_6a01482597e88190859b35b1c4aa8e84 completed May 11, 2026, 3:08 a.m.
Created at: April 10, 2026, 5:35 a.m.