Triple
T20905601
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gaegyeong |
E514789
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Kaesong |
—
|
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: Kaesong | Statement: [Gaegyeong, locatedIn, Kaesong]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kaesong Context triple: [Gaegyeong, locatedIn, Kaesong]
-
A.
Kaesong
chosen
Kaesong is a historic city in present-day North Korea that served as the capital of the medieval Korean kingdom of Goryeo and remains known for its cultural heritage and traditional architecture.
-
B.
Kyongsong
Kyongsong is a coastal town and county-level city in northeastern North Korea known for its hot springs and location along the Sea of Japan (East Sea).
-
C.
Hanseong
Hanseong was the historical name for Seoul when it served as the capital of the Joseon Dynasty in Korea.
-
D.
Tancheon
Tancheon is a river in South Korea that flows through the city of Seongnam and serves as a key urban waterway and recreational area.
-
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 (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_69e0b4f8a1108190bce3d31331290ced |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6e8ff36488190987ecdfcbed4220c |
completed | April 21, 2026, 3:03 a.m. |
Created at: April 16, 2026, 12:47 p.m.