Triple
T13344283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gyeongseong |
E317908
|
entity |
| Predicate | predecessor |
P97
|
FINISHED |
| Object | Hanseong |
E514441
|
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: Hanseong | Statement: [Gyeongseong, predecessor, Hanseong]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hanseong Context triple: [Gyeongseong, predecessor, Hanseong]
-
A.
Hanseong
chosen
Hanseong was the historical name for Seoul when it served as the capital of the Joseon Dynasty in Korea.
-
B.
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.
-
C.
Sinchon
Sinchon is a vibrant university district in Seoul, South Korea, known for its dense concentration of colleges, youth culture, shopping, and nightlife.
-
D.
Hongseong
Hongseong is a town in South Korea that serves as the administrative capital of South Chungcheong Province.
-
E.
Kaesong
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.
- 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_69d806b5a3c08190b42c267fb092f98a |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99e8839b48190b164414b418e756c |
completed | April 11, 2026, 1:06 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd4c1ee7048190b2571364b25bd49d |
completed | May 8, 2026, 2:36 a.m. |
Created at: April 9, 2026, 9:31 p.m.