Triple
T5575196
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jongno-gu |
E146300
|
entity |
| Predicate | hasKoreanName |
P17869
|
FINISHED |
| Object | 종로구 |
E350135
|
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: 종로구 | Statement: [Jongno-gu, hasKoreanName, 종로구]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 종로구 Context triple: [Jongno-gu, hasKoreanName, 종로구]
-
A.
Seodaemun-gu
Seodaemun-gu is a central district in Seoul, South Korea, known for its major universities, historical sites, and vibrant urban neighborhoods.
-
B.
Seocho District
Seocho District is a major affluent ward in southern Seoul, South Korea, known for its legal institutions, upscale residential areas, and proximity to the Gangnam business district.
-
C.
Seongdong District
Seongdong District is an urban ward in eastern central Seoul, South Korea, known for its mix of residential neighborhoods, commercial areas, and redevelopment zones along the Han River.
-
D.
Jongno District
chosen
Jongno District is a central historic and administrative area of Seoul, South Korea, known for its government institutions, cultural landmarks, and traditional neighborhoods.
-
E.
금정구
금정구는 부산광역시 북동부에 위치한 행정구로, 금정산과 범어사 등 자연·문화 유산이 풍부한 주거·교육 중심 지역이다.
- 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_69c008ffed108190a084602227af6157 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c02067e8d8819090a006cb266da5fe |
completed | March 22, 2026, 5:01 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c02852a6fc8190a543508ab3237f95 |
completed | March 22, 2026, 5:35 p.m. |
Created at: March 22, 2026, 3:37 p.m.