Triple
T21509907
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Pyongan Province |
E530687
|
entity |
| Predicate | hasCity |
P316
|
FINISHED |
| Object | Pyongsong |
—
|
NE NERFINISHED |
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: Pyongsong | Statement: [South Pyongan Province, hasCity, Pyongsong]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pyongsong Context triple: [South Pyongan Province, hasCity, Pyongsong]
-
A.
Pyongsong
chosen
Pyongsong is a North Korean city known as an administrative and industrial center near Pyongyang, with roles in science, education, and commerce.
-
B.
Phyongwon
Phyongwon is a city in North Korea known as an administrative and agricultural center within North Pyongan Province.
-
C.
Sŏngjin
Sŏngjin is the former name of Kim Chaek City, an industrial port city on North Korea’s east coast.
-
D.
Pak Hyŏkkŏse
Pak Hyŏkkŏse is the legendary founding monarch of the ancient Korean kingdom of Silla, traditionally said to have established the state in 57 BCE.
-
E.
Yŏngnŭng
Yŏngnŭng is the McCune–Reischauer romanization of Yeongneung, a royal tomb site in Paju, South Korea.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0c45c81f08190a6b8bbb70a45aae7 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9ea84dfbc8190a23d9a7d6eb2c2b5 |
completed | April 23, 2026, 9:46 a.m. |
Created at: April 16, 2026, 6:25 p.m.