Triple
T9087713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seo District, Busan |
E217800
|
entity |
| Predicate | nativeName |
P15
|
FINISHED |
| Object | 부산광역시 서구 |
E217800
|
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: [Seo District, Busan, nativeName, 부산광역시 서구]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 부산광역시 서구 Context triple: [Seo District, Busan, nativeName, 부산광역시 서구]
-
A.
부산광역시 북구
부산광역시 북구는 대한민국 부산광역시 북부에 위치한 행정구로, 주거 지역과 교육·상업 시설이 혼재한 도심 외곽 지역이다.
-
B.
부산광역시 연제구
부산광역시 연제구는 부산광역시 중앙부에 위치한 행정구로, 시청과 주요 공공기관이 밀집한 행정·주거 중심 지역이다.
-
C.
부산광역시 중구
부산광역시 중구는 부산광역시의 원도심이자 항만·상업 기능이 밀집한 중심 자치구이다.
-
D.
Seo District, Busan
chosen
Seo District, Busan is a central administrative and residential area of Busan, South Korea, known for its urban neighborhoods, commercial zones, and connectivity via the Busan Metro.
-
E.
Suyeong-gu, Busan
Suyeong-gu, Busan is a coastal district in southeastern Busan, South Korea, known for its urban residential areas, commercial centers, and proximity to popular beaches and scenic mountains.
- 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_69ca83d8ab5881909d8fddae363b32b1 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc965646408190b041ab0e2d5dbc94 |
completed | April 1, 2026, 3:51 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d017d500988190a6abf633f2226858 |
completed | April 3, 2026, 7:41 p.m. |
Created at: March 30, 2026, 7:13 p.m.