Triple
T13217705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 연제구 |
E314662
|
entity |
| Predicate | borderedBy |
P224
|
FINISHED |
| Object | 부산광역시 부산진구 |
E636867
|
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: [연제구, borderedBy, 부산광역시 부산진구]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 부산광역시 부산진구 Context triple: [연제구, borderedBy, 부산광역시 부산진구]
-
A.
부산광역시 연제구
부산광역시 연제구는 부산광역시 중앙부에 위치한 행정구로, 시청과 주요 공공기관이 밀집한 행정·주거 중심 지역이다.
-
B.
부산광역시 북구
부산광역시 북구는 대한민국 부산광역시 북부에 위치한 행정구로, 주거 지역과 교육·상업 시설이 혼재한 도심 외곽 지역이다.
-
C.
부산광역시 중구
부산광역시 중구는 부산광역시의 원도심이자 항만·상업 기능이 밀집한 중심 자치구이다.
-
D.
Busanjin-gu, Busan
chosen
Busanjin-gu, Busan is a central urban district of Busan, South Korea, known for its major commercial areas, dense residential neighborhoods, and key transportation hubs.
-
E.
Geumjeong District, Busan
Geumjeong District is a northeastern district of Busan, South Korea, known for its major university presence and proximity to the scenic Geumjeongsan mountain area.
- 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_69d806affc688190a25b6ccc588e9c72 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf392e08190949ee4d194566395 |
completed | April 10, 2026, 11:51 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6ff2085f88190be8cfc309d21f9cb |
completed | May 3, 2026, 7:54 a.m. |
Created at: April 9, 2026, 9:18 p.m.