Triple
T22315343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King of Joseon |
E551625
|
entity |
| Predicate | capital |
P234
|
FINISHED |
| Object | Hanseong |
—
|
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: Hanseong | Statement: [King of Joseon, capital, Hanseong]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hanseong Context triple: [King of Joseon, capital, Hanseong]
-
A.
Hanseong
chosen
Hanseong was the historical name for Seoul when it served as the capital of the Joseon Dynasty in Korea.
-
B.
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.
-
C.
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).
-
D.
Gaeseong
Gaeseong is a historic city on the Korean Peninsula that served as the capital of the Goryeo dynasty and is now located in southern North Korea near the border with South Korea.
-
E.
Gwangmyeong
Gwangmyeong is a city in South Korea known for its proximity to Seoul and attractions like the Gwangmyeong Cave, a former mine turned cultural and tourism complex.
- 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_69e11e4776588190abb21e5cea79973f |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1575287688190aa642bb49b24f5a1 |
completed | April 29, 2026, 12:56 a.m. |
Created at: April 16, 2026, 8:42 p.m.